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 commands/xlreon/chrome-actuator/chromegit clone --depth 1 https://github.com/xlreon/chrome-actuatorWrote 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/commands/xlreon/chrome-actuator/chrome)<a href="https://agentmods.dev/commands/xlreon/chrome-actuator/chrome"><img src="https://agentmods.dev/badge/commands/xlreon/chrome-actuator/chrome.svg" alt="Measured on agentmods" 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 | $0.00013 | $0.00087 |
| Opus 5 | $0.00006 | $0.00044 |
| Sonnet 5 | $0.00003 | $0.00017 |
| Haiku 4.5 | $0.00001 | $0.00009 |
Grade A, and why
chrome 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 3d 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
Chrome Actuator status.
- Confirm the unpacked extension is loaded from
packages/extension/distof this repo. - If tools fail with EXTENSION_DISCONNECTED, run
node packages/host/dist/install.jsfrom the repo root and fully quit + reopen Chrome. - Then
tabs_listto verify the bridge.
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.
- 3d ago First seen · 10 lines · 13 tokens per session scan A 89b1fd0b23a9
chrome is a command published in the GitHub repository xlreon/chrome-actuator (0 stars, last pushed 16d ago), licensed MIT. It adds 13 tokens to every session and 87 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-31.
Other commands, from other repositories
check-browser
Use Real Browser MCP to check what's currently showing in my browser.
qa
Dispatch a verifiable browser task to the qa-tester subagent. Use for regression checks, smoke tests, and any task with a clean pass/fail outcome. Supports an EXHAUSTIVE mode that verifies every control behind an honesty gate.
verify-pr
Verify a PR's frontend changes through browser automation.
record
Record browser actions into a test definition.
explore
Explore a web page using browser automation.
playbook
Manage Mochi playbooks (list, show, run, delete). Plays through the browser MCP tools.