Borrowing it
Nothing to install: this file belongs to lordamdal/chromeboost. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/lordamdal/chromeboost/main/CLAUDE.mdgit 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/instructions/lordamdal/chromeboost/claude-md)<a href="https://agentmods.dev/instructions/lordamdal/chromeboost/claude-md"><img src="https://agentmods.dev/badge/instructions/lordamdal/chromeboost/claude-md/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/instructions/lordamdal/chromeboost/claude-md"><img src="https://agentmods.dev/badge/instructions/lordamdal/chromeboost/claude-md.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.03902 | $0.03902 |
| Opus 5.5 | $0.01561 | $0.01561 |
| Sonnet 5.5 | $0.00780 | $0.00780 |
| Haiku 4.5 | $0.00390 | $0.00390 |
Grade A, and why
chromeboost CLAUDE.md 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 1mo 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 — 342 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ChromeBoost — repo-developer guide
This file is for developers working ON chromeboost. The usage reference for
agents (Claude Code, Codex, etc.) lives in
packages/plugin/skills/chromeboost/ (and skills-codex/chromeboost/ for
the Codex variant). When in doubt, the canonical user-facing docs are in
the skill, not here.
What chromeboost is
ChromeBoost is a Chrome extension + MCP server pair that lets coding
agents drive the user's real Chrome browser. The extension attaches via
CDP; the MCP server exposes 35 tools (click_element, fill_input,
type_text, get_page_text, hover, drag, probe_point, hud, etc.)
over the standard Model Context Protocol. Agents call those tools; the extension performs the operations
in the user's logged-in Chrome window.
The core differentiator is the click + keystroke pipeline: a humanlike
CDP bezier sequence with pointerType: "mouse" (firing PointerEvent
isPrimary=true alongside MouseEvent), settle-hover micro-tremor,
post-click jitter, and isTrusted=true keystrokes. This is what defeats
anti-bot checks on Reddit, X / Twitter, and similar isTrusted-strict
React UIs.
ChromeBoost adds two things on top of that inherited pipeline:
Occlusion-aware cursor control. Clicks hit-test before firing
(content/hittest.ts) instead of aiming at an element's geometric centre
and hoping nothing is on top. Covered targets are detected and reported;
covering layers are temporarily neutralised with pointer-events: none
so the same real CDP click reaches the target, then restored exactly.
hover and drag cover the UI that is not click-shaped at all.
A HUD the user owns. The on-page status panel (content/hud.ts) is
draggable, collapsible, dismissible, and persists its position — replacing
a fixed, pointer-events: none badge welded to the top-right corner.
Repository layout
packages/
extension/ # Chrome MV3 extension (TypeScript)
src/
background.ts # MCP message dispatcher, CDP helpers, ~3700 lines
content/ # Content-script handlers (shadow-piercing DOM ops)
hittest.ts # Occlusion-aware hit testing + overlay piercing
hud.ts # Draggable / hideable on-page HUD (closed shadow root)
offscreen.ts # Persistent WebSocket connection to MCP server
popup/ # Browser-action popup UI
page-shims.ts # MAIN-world page shims (focus, WebRTC, etc.)
build.mjs # esbuild
pack.mjs # Zip the dist/ for Chrome Web Store
manifest.json
mcp-server/ # MCP server bundled to packages/plugin/server/
src/
index.ts # Tool registration entry
ws-bridge.ts # WebSocket server (extension <-> MCP)
tools/ # Tool definitions per family
cursor.ts # hover, drag, probe_point, hud
types.ts # Message types between MCP and extension
package.json # Published to npm as "chromeboost"
plugin/ # Claude Code / Codex plugin manifest + skill
.claude-plugin/
plugin.json
skills/chromeboost/
SKILL.md # User-facing routing + common patterns
references/ # Topic-specific deep references
skills-codex/chromeboost/
SKILL.md # Codex variant
references/ # Same references, copied
server/
chromeboost.mjs # Bundled MCP server (esbuild output)
scripts/
build-server.sh # Bundle script
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.
- 1mo ago Changed · +19 lines · +269 tokens per session e079732f6012
- 1mo ago First seen · 323 lines · 3,633 tokens per session scan A edc34e4417cd
chromeboost CLAUDE.md is an instructions file published in the GitHub repository lordamdal/chromeboost (8 stars, last pushed 1mo ago), licensed MIT. It adds 3,902 tokens to every session, about $0.0156 per session on Opus 5.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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.