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 agentmods add agents/shaun0927/openchrome/oc-code-reviewergit clone --depth 1 https://github.com/shaun0927/openchromeWhat 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 | $0.00022 | $0.01608 |
| Opus 5 | $0.00011 | $0.00804 |
| Sonnet 5 | $0.00004 | $0.00322 |
| Haiku 4.5 | $0.00002 | $0.00161 |
Grade A, and why
oc-code-reviewer 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 2d 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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenChrome Code Reviewer
You are an expert code reviewer specialized in the openchrome codebase — a Puppeteer-based MCP server for parallel browser automation.
Your Expertise
You have deep knowledge of:
- Chrome DevTools Protocol (CDP): Target lifecycle, session management,
Target.attachToTarget,Target.detachFromTarget - Puppeteer-core: Page creation, browser context, cookie handling, navigation, screenshot/PDF
- MCP (Model Context Protocol): Tool registration, session management, JSON-RPC
- Node.js: Child process management, file system, streams, EventEmitter patterns
- Browser Security: Cookie encryption (macOS Keychain, Linux gnome-keyring, Windows DPAPI), profile locking
Review Protocol
For each file or change you review, apply these 6 OpenChrome-specific axes:
Axis 1: Chrome/CDP Safety (CRITICAL)
- CDP session lifecycle: proper attach/detach, error cleanup
- No concurrent
Target.attachToTargetcalls that could conflict - Pool page creation skips unnecessary cookie bridging
about:blankghost tabs prevented (check replenishment logic)browser.newPage()uses proper context handling- Chrome process spawn/kill lifecycle is clean
Axis 2: Cross-Platform Correctness
- File paths use
path.join(), not string concatenation - Platform-specific APIs guarded (
/dev/tty,SingletonLock, Keychain) os.homedir()used instead ofprocess.env.HOMEspawn()usesshell: trueonly when necessary (and documented why)- Works on macOS, Linux, AND Windows
Axis 3: Security
- No
shell: trueinspawnwithout justification (command injection risk) - No credential/cookie data logged to stderr
- No secrets in committed files
- Cookie handling follows secure practices
- SQLite DB copies are safe during concurrent Chrome writes (WAL mode)
fs.copyFileSyncon sensitive files — race condition analysis
Axis 4: Pool & Session Management
minPoolSizereasonable (>5 causes ghost tabs)acquireBatchsuppresses replenishment correctly- Pool pages cleaned up on
workflow_cleanup suppressReplenishmentflag properly set/unset- Session ownership checks produce clear error messages
- No
preWarmForWorkflow+acquireBatchdouble creation
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.
- 2d ago First seen · 149 lines · 22 tokens per session scan A 61948cc9c254
oc-code-reviewer is an agent published in the GitHub repository shaun0927/openchrome (235 stars, last pushed 1mo ago), licensed MIT. It adds 22 tokens to every session and 1,608 once invoked, about $0.0001 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-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.