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 leeguooooo/chrome-usenpx agentmods add plugins/leeguooooo/chrome-use/marketplacegit clone --depth 1 https://github.com/leeguooooo/chrome-useGrade A, and why
chrome-use 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.
What it actually says
{
"$schema": "https://anthropic.com/claude-code/marketplace.schema.json",
"name": "chrome-use",
"description": "Browser automation for AI agents",
"owner": {
"name": "leeguooooo",
"email": "[email protected]"
},
"plugins": [
{
"name": "chrome-use",
"description": "Automates browser interactions for web testing, form filling, screenshots, and data extraction",
"source": "./",
"strict": false,
"skills": ["./skills/chrome-use"],
"category": "development"
}
]
}
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 · 20 lines scan A 0a551564e44e
chrome-use is a plugin published in the GitHub repository leeguooooo/chrome-use (156 stars, last pushed 2d 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 comes from a forked repository.
Other plugins, from other repositories
vibe-browser
Claude Code plugins from Vibe Technologies for driving your real Chrome.
vibe-browser
Drive your real, logged-in Chrome from Claude Code. Navigate, click, type, screenshot and read pages in the browser you already use - including a browser on a different machine, with no inbound port open.
claude-in-chrome
Drive your real, logged-in Chrome from Claude Code, and list tabs across readable Chrome and Chromium profiles. Exposes the extension's browser tools through the Claude in Chrome bridge and adds a read-only listopentabs tool backed by local session data. Driving requires the connected extension and a running Chrome.
agentos-chrome-cdp
Control exact logged-in Chrome profiles with a Codex-compatible browser API.
claude-in-chrome-cli
Tools from the Claude in Chrome extension, as a Claude Code plugin or a Node.js CLI.
claude-bridge
Marketplace for Claude Bridge: autonomous browser handoff for Claude Code.