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 bakhtiersizhaev/chromewire-mcp --skill debug-codex-chrome-mcpgit clone --depth 1 https://github.com/bakhtiersizhaev/chromewire-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/bakhtiersizhaev/chromewire-mcp/debug-codex-chrome-mcp)<a href="https://agentmods.dev/skills/bakhtiersizhaev/chromewire-mcp/debug-codex-chrome-mcp"><img src="https://agentmods.dev/badge/skills/bakhtiersizhaev/chromewire-mcp/debug-codex-chrome-mcp/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/bakhtiersizhaev/chromewire-mcp/debug-codex-chrome-mcp"><img src="https://agentmods.dev/badge/skills/bakhtiersizhaev/chromewire-mcp/debug-codex-chrome-mcp.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.00033 | $0.00521 |
| Opus 5 | $0.00016 | $0.00260 |
| Sonnet 5 | $0.00007 | $0.00104 |
| Haiku 4.5 | $0.00003 | $0.00052 |
Grade A, and why
debug-codex-chrome-mcp 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 10d 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 10d ago First seen · 43 lines · 33 tokens per session scan A 5b789f7aff90
debug-codex-chrome-mcp is a skill published in the GitHub repository bakhtiersizhaev/chromewire-mcp (2 stars, last pushed 3mo ago), with no licence file. It adds 33 tokens to every session and 521 once invoked, about $0.0002 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
surf
Control Chrome browser via CLI for testing, automation, and debugging. Use when the user needs browser automation, screenshots, form filling, page inspection, network/CPU emulation, DevTools streaming, or AI queries via ChatGPT/Gemini/Perplexity/Grok/AI Studio.
debug-failed-action
When your last vsact returned an unexpected result (NOTFOUND, no visible state change, suspected silent failure), run this skill with the action's pre-token. Pulls console errors, network failures, and current performance into one report.
coding-browser-verify
Use this skill to reproduce or verify a browser-observable defect — a UI bug, console error, failed network call, or visual regression — using live browser inspection. It treats console/DOM/network content as untrusted data and requires an isolated browser profile; do not use it for a non-browser failure, or for…
chrome-bridge
Recipes for the user's real, logged-in Chrome through the chrome-bridge MCP tools and the zero-token chrome-bridge CLI. Use whenever the user wants to test, debug, audit, compare or automate something in a browser — a form "until the email arrives", a checkout with a test card, a pixel/GTM check, a cookie-banner…
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-control
Control and analyze a user-approved Google Chrome tab, or analyze supplied JavaScript, source maps, binary payloads, protocols, and WASM locally through chrome-agent-bridge MCP tools. Use for visible page control, script collection/search, CDP debugging, performance profiling, sensitive opt-in network inspection…