Borrowing it
Nothing to install: this file belongs to VitalyOstanin/mcp-chrome-debugger-protocol. 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/VitalyOstanin/mcp-chrome-debugger-protocol/master/AGENTS.mdgit clone --depth 1 https://github.com/VitalyOstanin/mcp-chrome-debugger-protocolWrote 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/vitalyostanin/mcp-chrome-debugger-protocol/agents-md)<a href="https://agentmods.dev/instructions/vitalyostanin/mcp-chrome-debugger-protocol/agents-md"><img src="https://agentmods.dev/badge/instructions/vitalyostanin/mcp-chrome-debugger-protocol/agents-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/vitalyostanin/mcp-chrome-debugger-protocol/agents-md"><img src="https://agentmods.dev/badge/instructions/vitalyostanin/mcp-chrome-debugger-protocol/agents-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.01601 | $0.01601 |
| Opus 5.5 | $0.00640 | $0.00640 |
| Sonnet 5.5 | $0.00320 | $0.00320 |
| Haiku 4.5 | $0.00160 | $0.00160 |
Grade A, and why
mcp-chrome-debugger-protocol AGENTS.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 2mo 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Contributor Notes
- Read
CLAUDE.mdfirst for project-specific rules and workflow. - Project language: English (code, comments, docs, commits).
- After making changes, run
npm run lint:fixlocally before commits.
Project Structure & Module Organization
src/: TypeScript sources for the MCP server, DAP client, CDP transport, and utilities.- Key modules:
mcp-server.ts,dap-client.ts,nodejs-debug-adapter.ts,cdp-transport.ts,source-map-resolver.ts.
- Key modules:
tests/: vitest tests (unit insrc/next to source, integration undertests/integration/), with fixtures intests/fixtures/.dist/: Compiled JS (generated bynpm run build).scripts/: Local helper scripts (dev-test.sh,mcp-logpoint-check.mjs).
Build, Test, and Development Commands
npm run build: Compile TypeScript todist/(runsprebuildclean step first).npm start: Run compiled server fromdist/index.js.npm run dev: Type-check/watch compile during development.npm run dev:server: Build then start the server.npm test: Run unit tests (vitest.config.ts).npm run test:integration: Run integration tests (vitest.integration.config.ts).npm run test:all: Run unit and integration tests sequentially.npm run lint/npm run lint:fix: Lint and auto-fix code style.npm run dev:test: Dev helper script that launches the test-app fixture under--inspect=9229for manual attach.
Coding Style & Naming Conventions
- Language: TypeScript (ES modules). Files use kebab-case (e.g.,
dap-client.ts). - Linting: ESLint (see
eslint.config.mjs). Use nullish coalescing (??), optional chaining (?.). - Blank lines: required before
return, before/after a block ofconst/let/var; never between adjacent declarations. - Prefer
const, modern ES syntax, and type-only imports/exports where appropriate.
Testing Guidelines
- Framework: vitest (
vitest.config.tsfor unit,vitest.integration.config.tsfor integration). Keep tests near related features undertests/integration/orsrc/*.test.ts. - Naming:
*.test.tswith descriptive, behavior-focused test names. - Run full suite locally (
npm run test:all) before opening PRs. - After substantial changes: run integration tests selectively for affected specs to iterate faster, for example:
npm run test:integration -- tests/integration/your-feature.test.tsnpm run test:integration -- -t "your test name pattern"npm run test:integration -- --reporter=verbose
- If no tests cover the change (new functionality), propose creating a new integration or unit test and add it alongside the feature.
- Resource limits in
vitest*.config.ts(maxWorkers: '10%'for unit,maxWorkers: 1+fileParallelism: falsefor integration) are intentional. Do not raise them.
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.
- 2mo ago First seen · 91 lines · 1,601 tokens per session scan A 3e22fc0bc958
mcp-chrome-debugger-protocol AGENTS.md is an instructions file published in the GitHub repository VitalyOstanin/mcp-chrome-debugger-protocol (2 stars, last pushed 20d ago), licensed MIT. It adds 1,601 tokens to every session, about $0.0064 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.
mcp-chrome-debugger-protocol AGENTS.md compared with instructions from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| mcp-chrome-debugger-protocol AGENTS.mdVitalyOstanin/mcp-chrome-debugger-protocol | Instructions file | 2 | 20d ago | MIT | A | 1,601 | Codex, OpenCode |
| vscode buildNext.instructions.mdmicrosoft/vscode | Instructions file | 195k | today | MIT | A | 9,719 | GitHub Copilot |
| vscode oss-third-party-notices.instructions.mdmicrosoft/vscode | Instructions file | 195k | today | MIT | A | 5,516 | GitHub Copilot |
| next.js AGENTS.mdvercel/next.js | Instructions file | 143k | today | MIT | A | 7,461 | Codex, OpenCode |
| langchain AGENTS.mdlangchain-ai/langchain | Instructions file | 149k | today | MIT | A | 4,680 | Codex, OpenCode |
| vscode copilot-instructions.mdmicrosoft/vscode | Instructions file | 195k | today | MIT | A | 3,093 | GitHub Copilot |
| vscode model-prompts.instructions.mdmicrosoft/vscode | Instructions file | 195k | today | MIT | A | 2,022 | GitHub Copilot |