Playwright E2E Testing
activepieces/activepieces
Playwright modern end-to-end testing framework with cross-browser automation, auto-wait, and built-in test runner
This skill should be used when the user asks about browser automation, testing web pages, extracting content, filling forms, taking screenshots, or monitoring console/network activity.
Install Browser Automation
$ npx skills add mozilla/firefox-devtools-mcp --skill browser-automation -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mozilla/firefox-devtools-mcp browser-automation --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mozilla/firefox-devtools-mcp.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/firefox-devtools-mcp/skills/browser-automation .claude/skills/browser-automation && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "browser-automation" agent skill from https://github.com/mozilla/firefox-devtools-mcp/tree/main/plugins/firefox-devtools-mcp/skills/browser-automation into .claude/skills/browser-automation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "browser-automation", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mozilla/firefox-devtools-mcp/tree/main/plugins/firefox-devtools-mcp/skills/browser-automationType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mozilla/firefox-devtools-mcp --skill browser-automation -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mozilla/firefox-devtools-mcp browser-automation --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mozilla/firefox-devtools-mcp.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/firefox-devtools-mcp/skills/browser-automation .agents/skills/browser-automation && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "browser-automation" agent skill from https://github.com/mozilla/firefox-devtools-mcp/tree/main/plugins/firefox-devtools-mcp/skills/browser-automation into .agents/skills/browser-automation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "browser-automation", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mozilla/firefox-devtools-mcp --skill browser-automation -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mozilla/firefox-devtools-mcp browser-automation --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mozilla/firefox-devtools-mcp.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/firefox-devtools-mcp/skills/browser-automation .cursor/skills/browser-automation && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "browser-automation" agent skill from https://github.com/mozilla/firefox-devtools-mcp/tree/main/plugins/firefox-devtools-mcp/skills/browser-automation into .cursor/skills/browser-automation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "browser-automation", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mozilla/firefox-devtools-mcp.git --path plugins/firefox-devtools-mcp/skills/browser-automation--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mozilla/firefox-devtools-mcp --skill browser-automation -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mozilla/firefox-devtools-mcp browser-automation --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mozilla/firefox-devtools-mcp.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/firefox-devtools-mcp/skills/browser-automation .gemini/skills/browser-automation && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "browser-automation" agent skill from https://github.com/mozilla/firefox-devtools-mcp/tree/main/plugins/firefox-devtools-mcp/skills/browser-automation into .gemini/skills/browser-automation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "browser-automation", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mozilla/firefox-devtools-mcp browser-automationInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mozilla/firefox-devtools-mcp --skill browser-automation -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mozilla/firefox-devtools-mcp.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/firefox-devtools-mcp/skills/browser-automation .github/skills/browser-automation && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "browser-automation" agent skill from https://github.com/mozilla/firefox-devtools-mcp/tree/main/plugins/firefox-devtools-mcp/skills/browser-automation into .github/skills/browser-automation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "browser-automation", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mozilla/firefox-devtools-mcp --skill browser-automation -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mozilla/firefox-devtools-mcp browser-automation --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mozilla/firefox-devtools-mcp.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/firefox-devtools-mcp/skills/browser-automation .opencode/skills/browser-automation && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "browser-automation" agent skill from https://github.com/mozilla/firefox-devtools-mcp/tree/main/plugins/firefox-devtools-mcp/skills/browser-automation into .opencode/skills/browser-automation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "browser-automation", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
browser-automation- GitHub stars
- 470
- Token cost
- ~807 tokens
- SKILL.md length
- 335 words
- Files
- 1
- Skills in repo
- 6
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
This skill should be used when the user asks about browser automation, testing web pages, extracting content, filling forms, taking screenshots, or monitoring console/network activity.
- Works in 3 steps: Navigate and Snapshot → Interact with Elements → Re-snapshot After Changes
- Asks about browser automation
- SKILL.md covers Before Starting, When to Use This Skill, Core Workflow and Quick Reference, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Browser Automation is an agent skill from mozilla/firefox-devtools-mcp. This skill should be used when the user asks about browser automation, testing web pages, extracting content, filling forms, taking screenshots, or monitoring console/network activity. Activates for E2E testing, form automation, browsing tasks, or debugging web applications.
Its SKILL.md is about 810 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Productivity & Automation, covering Browser automation and End-to-end testing. It works with Model Context Protocol. The repository describes itself as: Model Context Protocol server for Firefox DevTools - enables AI assistants to inspect and control Firefox browser through WebDriver BiDi.
When your agent uses it
- Asks about browser automation
- Testing web pages
- Extracting content
- Taking screenshots
Example prompts
- “/browser-automation”
Workflow steps
3 steps, taken from the step headings in SKILL.md.
- Navigate and Snapshot
- Interact with Elements
- Re-snapshot After Changes
What it can do on your machine
Read from SKILL.md and the folder at commit 5c69888. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Browser Automation loads about 807 tokens when it runs. Until then it costs about 74 tokens; SKILL.md has 335 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 335 words (~807 tokens).
“When the user asks about browser automation, use Firefox DevTools MCP to control a real Firefox browser.”
- name
- browser-automation
Files
Just SKILL.md in plugins/firefox-devtools-mcp/skills/browser-automation of mozilla/firefox-devtools-mcp.
Open the folder on GitHubat commit 5c69888
Compare with similar skills
Browser Automation next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Browser Automation this skillmozilla/firefox-devtools-mcp | 470 | — | ~807 | Automated safety check: Pass | Custom licence | |
| Playwright E2E Testingactivepieces/activepieces | 25k | — | ~6.8k | Automated safety check: Pass | Custom licence | |
| Webctlcosinusalpha/webctl | 419 | — | ~1.7k | Automated safety check: Pass | None | |
| Glance TestDebugBase/glance | 156 | — | ~827 | Automated safety check: Pass | MIT | |
| Playwright Testingchongdashu/vibejam-starter-pack | 149 | — | ~2.2k | Automated safety check: Pass | None | |
| Agentic Browser Testingpetrkindlmann/qa-skills | 165 | — | ~4.5k | Automated safety check: Pass | MIT |
Similar skills
Webctl
cosinusalpha/webctl
Browser automation via CLI. An agent skill from cosinusalpha/webctl.
Glance Test
DebugBase/glance
Run E2E browser tests on any web application using Glance MCP.
Playwright Testing
chongdashu/vibejam-starter-pack
Plan, implement, and debug frontend tests: unit/integration/E2E/visual/a11y.
Agentic Browser Testing
petrkindlmann/qa-skills
Goal-driven E2E testing where a browser agent (Playwright MCP / computer-use) reads a natural-language goal and explores the app via the accessibility tree to assert outcomes — no pre-written script.
Claw Browser Anchor
breakstageaxe61/genspark-claw
Make browser automation reliable — anchor every click, type, and scroll to stable DOM selectors and semantic roles instead of screen coordinates, so actions survive layout shifts, A/B tests, and…
More from mozilla/firefox-devtools-mcp
Web Performance
mozilla/firefox-devtools-mcp
Find and fix why a website is slow by capturing and analyzing a Firefox performance profile, or by analyzing a profile the user already has (a saved file or a profiler.firefox.com share link).
Firefox Devtools Diagnose
mozilla/firefox-devtools-mcp
Diagnose Firefox DevTools MCP setup issues. An agent skill from mozilla/firefox-devtools-mcp.
Debug
mozilla/firefox-devtools-mcp
Show console errors and failed network requests. An agent skill from mozilla/firefox-devtools-mcp.
Navigate
mozilla/firefox-devtools-mcp
Navigate Firefox to a URL and take a DOM snapshot for interaction
Screenshot
mozilla/firefox-devtools-mcp
Take a screenshot of a URL or the current page. An agent skill from mozilla/firefox-devtools-mcp.
Related
Works with
Categories
Questions about Browser Automation
What does Browser Automation do?
This skill should be used when the user asks about browser automation, testing web pages, extracting content, filling forms, taking screenshots, or monitoring console/network activity. Browser Automation is an agent skill from mozilla/firefox-devtools-mcp. This skill should be used when the user asks about browser automation, testing web pages, extracting content, filling forms, taking screenshots, or monitoring console/network activity.
When should I use Browser Automation?
Browser Automation fits situations like: asks about browser automation; testing web pages; extracting content; taking screenshots.
How do I install Browser Automation in Claude Code?
Run `npx skills add mozilla/firefox-devtools-mcp --skill browser-automation -a claude-code`. Or copy the skill folder (plugins/firefox-devtools-mcp/skills/browser-automation in mozilla/firefox-devtools-mcp) into .claude/skills/browser-automation in your project. Claude Code loads it when a task matches its description.
How do I install Browser Automation in Codex?
Run `npx skills add mozilla/firefox-devtools-mcp --skill browser-automation -a codex`. Or copy the skill folder (plugins/firefox-devtools-mcp/skills/browser-automation in mozilla/firefox-devtools-mcp) into .agents/skills/browser-automation in your project. Codex loads it when a task matches its description.
Can I use Browser Automation in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mozilla/firefox-devtools-mcp --skill browser-automation -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/browser-automation, .gemini/skills/browser-automation, .github/skills/browser-automation and .opencode/skills/browser-automation in your project.
What does Browser Automation need to run?
SKILL.md names no scripts, command-line tools or credentials: Browser Automation is instructions for the agent only.
Does Browser Automation access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Browser Automation safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Browser Automation use?
Browser Automation has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Browser Automation use?
About 807 tokens (SKILL.md is roughly 3.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Browser Automation?
Skills that share tags, products or a category with Browser Automation: Playwright E2E Testing (activepieces/activepieces, 25k stars), Webctl (cosinusalpha/webctl, 419 stars), Glance Test (DebugBase/glance, 156 stars) and Playwright Testing (chongdashu/vibejam-starter-pack, 149 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Browser Automation?
mozilla (a GitHub organization) maintains it in mozilla/firefox-devtools-mcp, which has 470 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on October 6, 2026.
Source: mozilla/firefox-devtools-mcp on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.