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.
git clone --depth 1 https://github.com/lordamdal/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/plugins/lordamdal/chromeboost/gemini-extension)<a href="https://agentmods.dev/plugins/lordamdal/chromeboost/gemini-extension"><img src="https://agentmods.dev/badge/plugins/lordamdal/chromeboost/gemini-extension/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/plugins/lordamdal/chromeboost/gemini-extension"><img src="https://agentmods.dev/badge/plugins/lordamdal/chromeboost/gemini-extension.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
chromeboost 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 18d 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
{
"name": "chromeboost",
"version": "1.1.2",
"description": "Give Gemini hands in your own browser. Drives your real, logged-in Chrome with human-shaped clicks, drags and keystrokes, and hit-tests before it clicks so scrims and sticky bars cannot swallow the click.",
"mcpServers": {
"chromeboost": {
"command": "node",
"args": ["${extensionPath}/packages/plugin/server/chromeboost.mjs"],
"env": {
"CHROMEBOOST_HOST": "gemini"
},
"timeout": 60000
}
},
"contextFileName": "GEMINI.md"
}
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.
- 18d ago Changed 94ef9edfbfbe
- 2mo ago First seen · 17 lines scan A c2d9f5ca5e29
chromeboost is a plugin published in the GitHub repository lordamdal/chromeboost (8 stars, last pushed 19d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-09-14.
chromeboost compared with plugins from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| chromeboostlordamdal/chromeboost | Plugin | 8 | 19d ago | MIT | A | — | Gemini CLI |
| browser-mcpAgent360dk/browser-mcp | Plugin | 64 | yesterday | MIT | A | — | Gemini CLI |
| mochiDevZonayed/Mochi | Plugin | 3 | 15d ago | MIT | A | — | Claude Code |
| chromeflowNeoDrew/chromeflow | Plugin | 3 | 11d ago | MIT | A | — | Claude Code |
| codex-browserDeliciousBuding/codex-browser-bridge | Plugin | 27 | yesterday | MIT | A | — | Claude Code |
| byobwxtsky/byob | Plugin | 145 | 1mo ago | MIT | A | — | Claude Code |
| browser-relayreliefeai/browser-relay | Plugin | 139 | 2mo ago | MIT | A | — | Claude Code |