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/operasoftware/opera-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/operasoftware/opera-devtools-mcp/gemini-extension)<a href="https://agentmods.dev/plugins/operasoftware/opera-devtools-mcp/gemini-extension"><img src="https://agentmods.dev/badge/plugins/operasoftware/opera-devtools-mcp/gemini-extension/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/operasoftware/opera-devtools-mcp/gemini-extension"><img src="https://agentmods.dev/badge/plugins/operasoftware/opera-devtools-mcp/gemini-extension.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
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.
This is a copy
100% identical to chrome-devtools-mcp — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
{
"name": "chrome-devtools-mcp",
"version": "1.7.0",
"mcpServers": {
"chrome-devtools": {
"command": "npx",
"args": [
"[email protected]"
]
}
}
}
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 · 13 lines scan A b0ef6937d710
chrome-devtools-mcp is a plugin published in the GitHub repository operasoftware/opera-devtools-mcp (9 stars, last pushed yesterday), 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. It is 100% identical to chrome-devtools-mcp, differing in 4 lines, and is treated as a copy.
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.
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.
firefox-devtools-troubleshoot
Diagnose and fix Firefox DevTools MCP setup issues. Use this if the firefox-devtools-mcp plugin is not working.
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.
vibelens
Gives Claude eyes on localhost. Captures a screenshot, console/network errors and a token-optimized DOM snapshot of your dev server so UI bugs get fixed from evidence instead of guesswork.