Firefox Devtools logo

Firefox Devtools

Organization
zenobi-us
firefox-devtools

Enables Firefox remote debugging workflows, when browser automation or protocol-level Firefox inspection is needed, resulting in configured Firefox RDP access and repeatable debugging steps.

Overview

Publisherzenobi-us
Repositorydotfiles
Skill namefirefox-devtools
Stars
67
Forks
6
Bundled files
10
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 10 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by zenobi-us on GitHub. Read the source before you install it.

Installation

Install the Firefox Devtools AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/zenobi-us/dotfiles.git /tmp/dotfiles
mkdir -p .claude/skills
cp -r /tmp/dotfiles/files/devtools/agent/bundles/developer/skills/browsers/firefox-devtools .claude/skills/firefox-devtools
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Firefox Devtools in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Firefox Devtools on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Firefox Devtools is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Firefox DevTools Integration Skill

Purpose

Run scripts/analysis.ts directly for test coverage analysis. Run scripts/test-analysis.ts directly to execute the Bun test suite. This skill enables seamless integration of Firefox Remote Debugging Protocol (RDP) for development workflows, similar to Chrome DevTools integration. It configures Firefox to accept remote debugging connections and provides tooling to interact with browser instances programmatically.

Prerequisites

  • Firefox 55+ (RDP support)
  • Port 6000 available (or custom port)
  • Remote debugging enabled
  • Development environment setup

Core Concepts

Firefox Remote Debugging Protocol (RDP)

Unlike Chrome's Chrome DevTools Protocol (CDP), Firefox uses its own RDP over WebSocket connections on port 6000 by default.

Key differences from Chrome:

  • Transport: WebSocket instead of WebSocket (similar, but different protocol implementation)
  • Default Port: 6000 (vs Chrome's 9222)
  • Connection Type: Target-agnostic (works with tabs, workers, extensions)
  • Authentication: Optional origin header validation
  • Tools Available: Inspector, Debugger, Console, Network, Performance, Storage

Configuration Modes

1. Standard Remote Debugging

Enable Firefox to accept remote debugging connections:

bash
firefox --remote-debugging-port 6000
2. Profile-Based Configuration

Create a Firefox profile with debugging pre-enabled:

bash
firefox -profile /path/to/profile -remote-debugging-port 6000
3. Environment Variable Setup
bash
export MOZ_PROFILER_STARTUP=1
export MOZ_REMOTE_DEBUG_PORT=6000
firefox

Implementation Steps

Step 1: Enable Remote Debugging

javascript
// Via about:config in Firefox
devtools.debugger.remote-enabled = true
devtools.chrome.enabled = true
devtools.debugger.prompt-connection = false

Step 2: Connect DevTools Client

javascript
// Node.js example using RDP client
const { RDPClient } = require('firefox-rdp');

const client = new RDPClient({
  host: 'localhost',
  port: 6000
});

client.connect()
  .then(() => console.log('Connected to Firefox'))
  .catch(err => console.error('Connection failed:', err));

Step 3: Programmatic Debugging

Access browser capabilities through RDP:

  • Inspector: DOM manipulation and inspection
  • Debugger: JavaScript breakpoints and stepping
  • Console: Execute scripts and view logs
  • Network: Monitor and intercept requests
  • Performance: Profile runtime performance
  • Storage: Access cookies, localStorage, sessionStorage

Integration Points

1. Mise Configuration

toml
[tools.firefox-debug]
version = "latest"
env = { MOZ_REMOTE_DEBUG_PORT = "6000" }

2. Comtrya Provisioning

yaml
action: shell
description: "Enable Firefox Remote Debugging"
command: |
  firefox-preferences \
    --set devtools.debugger.remote-enabled=true \
    --set devtools.chrome.enabled=true \
    --set devtools.debugger.prompt-connection=false

3. MCPort Configuration

Similar to chrome-devtools-mcporter, create Firefox equivalents:

json
{
  "firefox-debug": {
    "binary": "firefox",
    "args": ["--remote-debugging-port", "6000"],
    "port": 6000,
    "protocol": "rdp"
  }
}

Common Tasks

Inspect DOM Elements

javascript
const { Inspector } = await client.getActor('inspector');
const nodeActor = await inspector.querySelector('body');
const attributes = await nodeActor.getAttributes();

Set JavaScript Breakpoint

javascript
const { Debugger } = await client.getActor('debugger');
const script = await debugger.getScript({ url: 'file.js' });
await debugger.setBreakpoint({ location: { scriptId: script.id, line: 10 } });

Execute Console Commands

javascript
const { Console } = await client.getActor('console');
const result = await console.evaluateJS('window.location.href');
console.log(result.value);

Monitor Network Requests

javascript
const { NetworkMonitor } = await client.getActor('networkMonitor');
networkMonitor.on('request', (req) => {
  console.log(`${req.method} ${req.url}`);
});

Tools and Libraries

RDP Clients

  • firefox-rdp - Raw RDP protocol client
  • webext-run - Run and debug WebExtensions
  • firefox-launcher - Programmatic Firefox launching

Integration Tools

  • firefox-devtools-adapter - Bridge between CDP and RDP
  • debug-protocol-converter - Convert between Chrome CDP and Firefox RDP

Development Tools

  • Firefox DevTools itself (can connect to remote instances)
  • Visual Studio Code extensions (Debugger for Firefox)
  • WebStorm/IntelliJ built-in Firefox debugging

Troubleshooting

Connection Refused

Cause: Firefox not listening on RDP port Solution:

bash
# Verify Firefox is running with debugging enabled
ps aux | grep firefox.*6000
# Or explicitly launch with port
firefox --remote-debugging-port 6000 &

Port Already in Use

Solution: Use custom port

bash
firefox --remote-debugging-port 7000 &
# Then connect to localhost:7000

Debugger Not Responding

Solution: Ensure prerequisites are met

bash
# Check about:config settings
about:config → devtools.debugger.remote-enabled = true
# Restart Firefox and reconnect

Authentication/Origin Errors

Solution: Configure CORS for RDP

javascript
client.setOriginHeader('http://localhost:3000');

Examples

Full Debugging Session

javascript
const { RDPClient } = require('firefox-rdp');

async function debugFirefox() {
  const client = new RDPClient({ host: 'localhost', port: 6000 });
  
  try {
    await client.connect();
    const tabs = await client.listTabs();
    const tab = tabs[0];
    
    const inspector = await tab.getActor('inspector');
    const console = await tab.getActor('console');
    
    // Inspect element
    const body = await inspector.querySelector('body');
    console.log('Body classes:', await body.getAttributes());
    
    // Execute console command
    const result = await console.evaluateJS('document.title');
    console.log('Page title:', result.value);
    
  } finally {
    await client.disconnect();
  }
}

debugFirefox().catch(console.error);

Integration with Build Tools

javascript
// webpack.config.js
module.exports = {
  devServer: {
    before(app) {
      app.use((req, res, next) => {
        res.setHeader('X-Debugger-Enabled', 'true');
        next();
      });
    }
  },
  // Connect to Firefox RDP for debugging
  devtool: 'eval-source-map'
};

Performance Considerations

  1. RDP Overhead: Remote debugging adds minimal overhead but disable in production
  2. Port Binding: Use high-numbered ports (>6000) to avoid conflicts
  3. Connection Pooling: Reuse RDP connections across multiple operations
  4. Memory: Firefox with debugging enabled uses ~10-15% more memory

Security Notes

  • Local Development Only: Only enable RDP on localhost in development
  • Network Isolation: Don't expose RDP port to untrusted networks
  • Session Management: Disconnect clients when finished
  • Credential Storage: Never log debugging credentials

References

Related Skills

  • files/devtools/chrome-devtools-mcporter - Chrome equivalent
  • superpowers/systematic-debugging - General debugging methodology
  • experts/quality-security/debugger - Debugging expert guidance
  • superpowers/frontend-developer - Frontend development context

Skill Metadata

  • Category: DevTools Integration
  • Complexity: Intermediate
  • Domain: Browser Debugging, Development Tools
  • Platforms: Linux, macOS, Windows
  • Languages: JavaScript, TypeScript, Python (via RDP client)
  • Last Updated: 2025-12-14

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Firefox Devtools AI skill do?

Enables Firefox remote debugging workflows, when browser automation or protocol-level Firefox inspection is needed, resulting in configured Firefox RDP access and repeatable debugging steps.

Why use Firefox Devtools on TypingMind?

Because you install it once and use it with any model. Firefox Devtools is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Firefox Devtools in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/zenobi-us/dotfiles/tree/master/files/devtools/agent/bundles/developer/skills/browsers/firefox-devtools. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Firefox Devtools?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Firefox Devtools?

As many as you like. As long as a model supports skills, you can use Firefox Devtools with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Firefox Devtools AI skill free?

Yes. It is published on GitHub by zenobi-us under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇