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.
git clone --depth 1 https://github.com/ctrlShiftBryan/chrome-devtools-mcpWrote 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/plugins/ctrlshiftbryan/chrome-devtools-mcp/marketplace)<a href="https://agentmods.dev/plugins/ctrlshiftbryan/chrome-devtools-mcp/marketplace"><img src="https://agentmods.dev/badge/plugins/ctrlshiftbryan/chrome-devtools-mcp/marketplace/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/plugins/ctrlshiftbryan/chrome-devtools-mcp/marketplace"><img src="https://agentmods.dev/badge/plugins/ctrlshiftbryan/chrome-devtools-mcp/marketplace.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
chrome-devtools-plugins marketplace 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 1mo 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- chrome-devtools-plugins marketplace — 100% identical, 0 lines differ
- chrome-devtools-plugins marketplace — 100% identical, 0 lines differ
What it actually says
{
"name": "chrome-devtools-plugins",
"version": "1.0.0",
"description": "Bundled plugins for actuating and debugging the Chrome browser.",
"owner": {
"name": "Chrome DevTools Team",
"email": "[email protected]"
},
"plugins": [
{
"name": "chrome-devtools-mcp",
"source": {
"source": "github",
"repo": "ChromeDevTools/chrome-devtools-mcp"
},
"description": "Reliable automation, in-depth debugging, and performance analysis in Chrome using Chrome DevTools and Puppeteer"
}
]
}
What ships with it
1 file beside marketplace.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 20 lines scan A fc089c64b5ab
chrome-devtools-plugins marketplace is a plugin published in the GitHub repository ctrlShiftBryan/chrome-devtools-mcp (3 stars, last pushed 10mo ago), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-08-31.
Other plugins, from other repositories
chrome-devtools-mcp
Reliable automation, in-depth debugging, and performance analysis in Chrome using Chrome DevTools and Puppeteer.
chrome-devtools-mcp
MCP configuration declaring 1 server: chrome-devtools.
firefox-devtools-mcp
Control Firefox for browsing, web testing, and debugging. Fill forms, capture network and console activity, take screenshots, run scripts, and profile performance. Supports Android devices.
firefox-devtools-troubleshoot
Diagnose and fix Firefox DevTools MCP setup issues. Use this if the firefox-devtools-mcp plugin is not working.
devharness
Run and debug a live app from inside Claude Code: breakpoints and variable inspection in Chrome and Node.js, managed dev servers, and replayable call history so setup is never re-driven by hand.
mobius-mcp
Scenario-focused skills for driving and debugging a running web app via the mobius-mcp MCP server — broken flows, QA walkthroughs, bug repros, perf stakeouts, and page audits.