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.
npx skills add ShalomObongo/chrome-bridge-mcp --skill control-chrome-bridgegit clone --depth 1 https://github.com/ShalomObongo/chrome-bridge-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/skills/shalomobongo/chrome-bridge-mcp/control-chrome-bridge)<a href="https://agentmods.dev/skills/shalomobongo/chrome-bridge-mcp/control-chrome-bridge"><img src="https://agentmods.dev/badge/skills/shalomobongo/chrome-bridge-mcp/control-chrome-bridge/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/skills/shalomobongo/chrome-bridge-mcp/control-chrome-bridge"><img src="https://agentmods.dev/badge/skills/shalomobongo/chrome-bridge-mcp/control-chrome-bridge.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00114 | $0.02188 |
| Opus 5 | $0.00057 | $0.01094 |
| Sonnet 5 | $0.00023 | $0.00438 |
| Haiku 4.5 | $0.00011 | $0.00219 |
Grade A, and why
control-chrome-bridge 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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Control Chrome (chrome-bridge)
This skill governs the chrome-bridge MCP server, which controls the user's real, running Chrome
over the Chrome DevTools Protocol. There is no sandbox: the tabs are theirs, the cookies are theirs,
and every session they are signed into is reachable. Treat that as the defining constraint.
Choose the right tool first
Reaching for the browser is not free — it is slower than an API and it exposes authenticated surfaces. Before starting:
- If a purpose-built connector, API or CLI can do the job, use it instead.
- If one exists but fails on expired auth, ask the user to re-authenticate rather than routing around it through the browser.
- A URL in the conversation is context, not an instruction to open a browser. Re-evaluate per operation; earlier browser use does not make later work browser-first.
- Do use the browser when the task is genuinely about the page (inspect, navigate, click, fill, screenshot), when the resource is only reachable behind the user's existing login, or when you are testing a local app the user is developing.
Core loop
browser_tabs → browser_attach (or browser_new_tab) → browser_snapshot
→ act (click / type / select / hover / press_key / scroll)
→ read the snapshot that comes back → repeat → browser_detach
browser_tabslists every open tab. Read it before assuming anything about what is open.browser_attachtakes control of an existing tab — this is what reuses the user's logins. OmittabIdto take the active tab.browser_new_tabopens a fresh one instead, placed in a labelled tab group so the user can tell it apart from their own.browser_snapshotis your eyes. It returns a compact outline of everything visible, with a[ref=…]on each actionable element. It is far cheaper than a screenshot and is the correct default for understanding page state.- Every interaction tool returns a fresh snapshot, so you see the consequence of an action without a second call. Read it; do not immediately re-snapshot out of habit.
browser_detachwhen you are done. It releases the tab, restores the page favicon and dismisses Chrome's "being debugged" banner.
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.
- 9d ago First seen · 160 lines · 114 tokens per session scan A ea24d075e581
control-chrome-bridge is a skill published in the GitHub repository ShalomObongo/chrome-bridge-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 114 tokens to every session and 2,188 once invoked, about $0.0006 per session on Opus 5. 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 skills, from other repositories
owb
Open Web Bridge (OWB) — drive the user's own real browser with the owb command. Read pages behind their existing logins, gather and cross-check information, fill forms, walk multi-step flows, debug their site, audit responsive/accessibility behavior, and capture or reverse-engineer network traffic. Use this whenever…
codex-control-chrome-mcp
Use Codex Control Chrome MCP to control the user's normal Chrome profile through the Codex Chrome extension. Use when a task needs existing Chrome tabs, cookies, logged-in sessions, installed extensions, CDP commands, page inspection, navigation, screenshots, network/console events, or browser automation from an MCP…
chrome-agent
Local browser automation with structured, verified outcomes. Use for web navigation, scraping and extraction, form interaction, screenshots and downloads, network or console checks, responsive testing, or page-scoped device emulation.
scrape-structured-data
Get the repeating records off a web page (product grids, search results, job listings, news feeds, tables) as JSON, without writing CSS selectors and without spending a model call to read the HTML. Works on sites with no API, including ones behind a login or bot protection. Runs locally, one binary, no API key. Use…
codex-browser
Control Chrome via Codex Desktop's browser bridge. 52 MCP tools for tabs, navigation, DOM, input, CDP, network, file upload, dialog handling, and diagnostics.
browser-automation
Use this skill when the user asks to interact with a browser, take screenshots, inspect a page, capture network traffic, detect frameworks, click elements, fill forms, record browser sessions, or automate any browser task. Orchestrates Crawlio Browser's 150 browser tools via the search + execute + connecttab interface.