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/sshh12/claude-pluginsWrote 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/sshh12/claude-plugins/brw)<a href="https://agentmods.dev/plugins/sshh12/claude-plugins/brw"><img src="https://agentmods.dev/badge/plugins/sshh12/claude-plugins/brw/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/sshh12/claude-plugins/brw"><img src="https://agentmods.dev/badge/plugins/sshh12/claude-plugins/brw.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
brw 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.
What it actually says
{
"name": "brw",
"version": "0.9.0",
"description": "Browser automation for Claude Code via Chrome DevTools Protocol",
"author": {
"name": "shrivu"
},
"repository": "https://github.com/shrivu/claude-plugins",
"license": "MIT",
"keywords": ["browser", "automation", "chrome", "cdp", "web"],
"hooks": {
"SessionStart": [
{
"hooks": [
{
"type": "command",
"command": "node -e 'const v=parseInt(process.versions.node);if(v<18){console.error(\"brw requires Node.js 18+, found \"+process.version);process.exit(1)}' 2>/dev/null || echo 'Node.js 18+ not found. brw requires Node.js 18+ to run.'"
}
]
}
]
}
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 68 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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 · 24 lines scan A bb366e58ee2a
brw is a plugin published in the GitHub repository sshh12/claude-plugins (24 stars, last pushed 3mo ago), licensed MIT. 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-30.
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.
browser-harness
Direct browser control via CDP. Drives the user's real Chrome (or a Browser Use cloud browser) with coordinate clicks, screenshots, and Python helpers — no selector hunting. Requires the one-time browser-harness CLI install (see the skill's references/install.md).
unbrowse
Websites as APIs: read pages, run site tasks via learned APIs, and a cloud browser with saved logins.
notte
Browser automation for AI agents — real cloud or local browsers, observe/click/fill/scrape primitives, structured Pydantic extraction from dynamic pages, captcha solving and stealth mode, authenticated sessions via Vault, and one-command deployment of any browser automation as a scheduled, API-callable Notte Function.
melaya
Build, run and fix AI agent pipelines from 8k+ tools, and let your AI operate your Android phone and browser.