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.
/plugin marketplace add nimbus21/chrome-devtools-mcpnpx agentmods add plugins/nimbus21/chrome-devtools-mcp/marketplacegit clone --depth 1 https://github.com/nimbus21/chrome-devtools-mcpGrade A, and why
chrome-devtools-plugins 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 yesterday.
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
86% identical to chrome-devtools-plugins — 3 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-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": "./",
"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.
- yesterday First seen · 17 lines scan A 3a26c384e4ff
chrome-devtools-plugins is a plugin published in the GitHub repository nimbus21/chrome-devtools-mcp (0 stars, last pushed 4mo 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. It is 86% identical to chrome-devtools-plugins, differing in 3 lines, and is treated as a copy.
Other plugins, from other repositories
cli
Run HeadlessX website, search, YouTube, and jobs workflows from the terminal.
hhru
Plugin marketplace listing 1 plugin: hhru-cc-plugin.
dhm
Plugin marketplace listing 1 plugin: dear-hiring-manager.
kernel-sdks
TypeScript and Python SDK skills for building browser automation with Kernel's Typescript and Python SDKs.
webmcpify
Plugin marketplace listing 1 plugin: webmcpify.
realbrowser
Target-first local Chrome/Chromium browser control with signed-in profiles, labeled tabs, and guarded actions.