Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add lordamdal/chromeboost/plugin install chromeboostWrote 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/lordamdal/chromeboost/chromeboost-setup)<a href="https://agentmods.dev/commands/lordamdal/chromeboost/chromeboost-setup"><img src="https://agentmods.dev/badge/commands/lordamdal/chromeboost/chromeboost-setup.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.1 | $0.00014 | $0.00994 |
| Opus 5 | $0.00007 | $0.00497 |
| Sonnet 5 | $0.00003 | $0.00199 |
| Haiku 4.5 | $0.00001 | $0.00099 |
Grade A, and why
chromeboost-setup 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Finish ChromeBoost setup
The MCP server half of ChromeBoost is already installed (that is this plugin). What is left is the Chrome extension, the half that touches the browser. It is on the Chrome Web Store, so this is a one-click install.
Work through this now, without asking the user whether to proceed.
1. Check whether it is already done
Call list_tabs first. If it returns their tabs, the extension is installed and
bound: say so and skip to the closing suggestion in step 4. Users often arrive
here already set up, and walking them through an install they have finished is
noise.
2. Install from the Chrome Web Store
Give them this link and ask them to click Add to Chrome:
https://chromewebstore.google.com/detail/chromeboost/alphgffnpbhpfaimmaaibbcdmpmcbndo
Then have them pin ChromeBoost to the toolbar so the popup is one click away.
That is the whole install. No developer mode, no folder to keep, and it updates itself. If they would rather run from local files, see Loading unpacked instead at the bottom.
If they already had the unpacked copy loaded, they need to remove it at
chrome://extensions now. Both copies connect to the same local port, the
server keeps only one connection, and each new one evicts the other, so they
reconnect in a loop and tool calls land on whichever won the last race. Two
ChromeBoost cards on that page is the tell.
3. Connect a window
Tell them to click the ChromeBoost toolbar icon. This session should appear with a green dot on a port in the 7970-7980 range. They click Use this window next to it to bind the Chrome window they want driven.
4. Verify it actually works
Once they say it is installed, confirm the link yourself instead of taking it
on trust: call list_tabs. If it returns their open tabs, setup is done. Say so
plainly and suggest a first prompt, for example "open news.ycombinator.com and
give me the top 5 stories".
If list_tabs errors or times out, the extension is installed but not
connected. Have them reload it at chrome://extensions using the circular
arrow on the ChromeBoost card. It reconnects on a backoff timer and a reload
forces it immediately. Then try list_tabs again.
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 Changed · -5 tokens per session f684468b50a5
- 6d ago First seen · 95 lines · 19 tokens per session scan A 6454b2e9f615
chromeboost-setup is a command published in the GitHub repository lordamdal/chromeboost (8 stars, last pushed yesterday), licensed MIT. It adds 14 tokens to every session and 994 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.
playbook
Manage Mochi playbooks (list, show, run, delete). Plays through the browser MCP tools.
unschedule-playbook
Cancel a scheduled playbook routine.
browse
You have access to a browser via the MCP Browser Bridge tools. Use them to interact with web pages.
chrome
Check Chrome Actuator connection and remind how to install the native host.