Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/jpoutrin/product-forge/install-chrome-devtools-mcpnpx skills add jpoutrin/product-forge --skill install-chrome-devtools-mcpgit clone --depth 1 https://github.com/jpoutrin/product-forgeWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/jpoutrin/product-forge/install-chrome-devtools-mcp)<a href="https://agentmods.dev/skills/jpoutrin/product-forge/install-chrome-devtools-mcp"><img src="https://agentmods.dev/badge/skills/jpoutrin/product-forge/install-chrome-devtools-mcp.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00022 | $0.01743 |
| Opus 5 | $0.00011 | $0.00872 |
| Sonnet 5 | $0.00004 | $0.00349 |
| Haiku 4.5 | $0.00002 | $0.00174 |
Grade A, and why
install-chrome-devtools-mcp scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 253 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Install Chrome DevTools MCP Server
Install the Chrome DevTools MCP server to enable debugging and network inspection capabilities.
What This Does
The Chrome DevTools MCP server provides:
- Console inspection - View errors, warnings, and log messages
- Network analysis - Inspect HTTP requests and responses
- JavaScript evaluation - Run code in page context
- Performance tracing - Analyze page performance
- Screenshots - Capture page state
Installation Command
Run this command to install:
claude mcp add chrome-devtools -- npx -y chrome-devtools-mcp@latest
Scope Options
--scope local(default): Available only in current project--scope project: Shared with team via.mcp.json--scope user: Available across all your projects
# Install for user (all projects)
claude mcp add chrome-devtools --scope user -- npx -y chrome-devtools-mcp@latest
# Install for project (team shared)
claude mcp add chrome-devtools --scope project -- npx -y chrome-devtools-mcp@latest
Common Configurations
Headless Mode
For headless operation (no visible browser):
claude mcp add chrome-devtools -- npx -y chrome-devtools-mcp@latest --headless
Auto-Connect to Running Chrome
Connect to an already-running Chrome instance (Chrome 145+):
claude mcp add chrome-devtools -- npx -y chrome-devtools-mcp@latest --autoConnect
Connect to Specific Browser URL
For sandboxed environments or remote debugging:
claude mcp add chrome-devtools -- npx -y chrome-devtools-mcp@latest --browserUrl http://127.0.0.1:9222
Custom Viewport
Set initial window size:
claude mcp add chrome-devtools -- npx -y chrome-devtools-mcp@latest --viewport 1920x1080
Isolated Sessions (No Persistence)
Use temporary profile that cleans up automatically:
claude mcp add chrome-devtools -- npx -y chrome-devtools-mcp@latest --isolated
Verify Installation
After installation:
- Restart Claude Code
- Run
/mcpto see the chrome-devtools server - Test with: "Navigate to google.com and list console messages"
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2d ago First seen · 253 lines · 22 tokens per session scan A 45f648856441
install-chrome-devtools-mcp is a skill published in the GitHub repository jpoutrin/product-forge (15 stars, last pushed 6mo ago), licensed MIT. It adds 22 tokens to every session and 1,743 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
runtime-debug
Debug and verification workflow for runtime-bundle and module-resolution regressions. Use when diagnosing unexpected module inclusions, bundle size regressions, or CI failures related to NEXTSKIPISOLATE, nft.json traces, or runtime bundle selection (module.compiled.js). Covers CI env mirroring, full stack traces via…
chrome-devtools-cli
Use this skill to write shell scripts or run shell commands to automate tasks in the browser or otherwise use Chrome DevTools via CLI.
agent-browser-electron
Use when Codex needs to inspect, debug, or automate an Electron app through agent-browser and Chrome DevTools Protocol, especially when the app has multiple BrowserWindow instances, lazy-created windows, duplicate URLs, or misleading agent-browser tab list output. Covers mapping Electron windows to raw CDP targets…
a11y-debugging
Uses Chrome DevTools MCP for accessibility (a11y) debugging and auditing based on web.dev guidelines. Use when testing semantic HTML, ARIA labels, focus states, keyboard navigation, tap targets, and color contrast.
chrome-devtools
Uses Chrome DevTools via MCP for efficient debugging, troubleshooting and browser automation. Use when debugging web pages, automating browser interactions, analyzing performance, or inspecting network requests. This skill does not apply to --slim mode (MCP configuration).
nullaway
Guide for resolving NullAway static analysis errors. Best practices for: Passing ObservableSupplier/Supplier Dereferencing potentially @Nullable values Adding @NullMarked to Java code.