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/Stigmavlc/claude-bridgeWrote 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/stigmavlc/claude-bridge/marketplace)<a href="https://agentmods.dev/plugins/stigmavlc/claude-bridge/marketplace"><img src="https://agentmods.dev/badge/plugins/stigmavlc/claude-bridge/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/stigmavlc/claude-bridge/marketplace"><img src="https://agentmods.dev/badge/plugins/stigmavlc/claude-bridge/marketplace.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
claude-bridge 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.
What it actually says
{
"name": "claude-bridge",
"description": "Marketplace for Claude Bridge: autonomous browser handoff for Claude Code.",
"owner": {
"name": "Ivan Aguilar",
"email": "[email protected]"
},
"plugins": [
{
"name": "claude-bridge",
"source": {
"source": "github",
"repo": "Stigmavlc/claude-bridge"
},
"description": "When a task needs the web, Claude Code drives the browser itself: your real logged-in Chrome for account work, a headless browser for public lookups. Bundles a headless Chrome DevTools MCP engine and a routing skill; the logged-in path uses the Claude in Chrome extension via `/chrome`.",
"version": "0.1.0",
"author": {
"name": "Ivan Aguilar"
},
"keywords": ["browser", "automation", "chrome", "claude-in-chrome", "playwright"]
}
]
}
The plugins it lists here
This marketplace lists 1 plugin kept in the same repository. Each has its own page, its own measurements and its own install command.
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 · 24 lines scan A 398d7c6e73c9
claude-bridge marketplace is a plugin published in the GitHub repository Stigmavlc/claude-bridge (2 stars, last pushed 2mo 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-31.
Other plugins, from other repositories
fast-browser
Fast Playwright browser automation for Claude Code and Codex.
familiar
Control your real macOS Google Chrome via AppleScript — tab-scoped browser automation without the DevTools Protocol or Playwright.
agentos-chrome-cdp
Control exact logged-in Chrome profiles with a Codex-compatible browser API.
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.
supersurf
Skills for driving a real Chrome browser through the SuperSurf MCP server.
chrome-devtools-mcp
MCP configuration declaring 1 server: chrome-devtools.