Borrowing it
Nothing to install: this file belongs to TranHuyQn/cc-chrome-extension. 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/TranHuyQn/cc-chrome-extension/claude/claude-code-chrome-extension-q9a5sg/CLAUDE.mdgit clone --depth 1 https://github.com/TranHuyQn/cc-chrome-extensionWrote 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/tranhuyqn/cc-chrome-extension/claude-md)<a href="https://agentmods.dev/instructions/tranhuyqn/cc-chrome-extension/claude-md"><img src="https://agentmods.dev/badge/instructions/tranhuyqn/cc-chrome-extension/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/tranhuyqn/cc-chrome-extension/claude-md"><img src="https://agentmods.dev/badge/instructions/tranhuyqn/cc-chrome-extension/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.14694 | $0.14694 |
| Opus 5 | $0.07347 | $0.07347 |
| Sonnet 5 | $0.02939 | $0.02939 |
| Haiku 4.5 | $0.01469 | $0.01469 |
Grade D, and why
cc-chrome-extension CLAUDE.md scanned grade D with 3 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 10d 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
`curl -fsSL .../releases/latest/download/install.sh | bash` and Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
(`~/.claude/settings.json`) can carry `enabledPlugins`, and a plugin's Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
`curl -fsSL .../releases/latest/download/install.sh | bash` and How it starts
The opening of the file, as written. The whole thing — 816 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
What this is
An MCP server (server/) + Chrome MV3 extension (extension/) that lets Claude Code drive Chrome
without any claude.ai login. Every MCP tool call is forwarded over WebSocket to the extension, which
executes it with chrome.tabs / chrome.scripting / chrome.debugger and returns JSON.
One runtime mode: mainHttp() in server/index.js runs an HTTP + WebSocket server, bound to
127.0.0.1 by default (port 23949), that every Claude Code session and the extension both talk to.
There is no mainStdio() — stdio mode (single process on stdout, no auth) was removed before 1.0.0. The
distribution model changed with it: scripts/install.sh installs a per-user background service (see
"Setup and commands" below) instead of everyone pointing at one shared server. The shared-server shape
is gone, not deprecated — deploy/, the Cloudflare tunnel doc, POST /pair and every dynamic
token went with it in 1.0.0. TokenStore now only reads tokens configured up front, which for a normal
install is the one token install.sh writes to tokens.json.
Setup and commands
Three separate package.json files — installing at the root is not enough:
npm install # root: build tooling only (adm-zip, crx)
cd server && npm install # MCP server runtime deps (@modelcontextprotocol/sdk, ws, zod)
cd test && npm install # e2e deps (playwright)
npm run build # package extension -> dist/*.zip + signed dist/*.crx
npm run lint # eslint (flat config in eslint.config.mjs); must stay at 0 errors
npm test # build.test + origin.test + e2e + e2e-http — needs real Chromium
npm run test:e2e # a single suite: also test:build, test:origin, test:http
Tests launch a real Chromium with the extension loaded. All four files under test/ read
CHROME_PATH for the browser binary (falls back to Playwright's own managed Chromium when unset)
and HEADED=1 to run with a visible window instead of headless:
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.
- 10d ago First seen · 816 lines · 14,694 tokens per session scan D a1abbdebfe5b
cc-chrome-extension CLAUDE.md is an instructions file published in the GitHub repository TranHuyQn/cc-chrome-extension (4 stars, last pushed 11d ago), licensed MIT. It adds 14,694 tokens to every session, about $0.0735 per session on Opus 5. A static security scan graded it D with 3 findings (downloads and executes remote code, reads agent configuration directories, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
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.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
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.