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.
npx agentmods add instructions/bherbruck/mcp-debugger/claude-mdgit clone --depth 1 https://github.com/bherbruck/mcp-debuggerWrote 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/bherbruck/mcp-debugger/claude-md)<a href="https://agentmods.dev/instructions/bherbruck/mcp-debugger/claude-md"><img src="https://agentmods.dev/badge/instructions/bherbruck/mcp-debugger/claude-md.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 | $0.00631 | $0.00631 |
| Opus 5 | $0.00316 | $0.00316 |
| Sonnet 5 | $0.00126 | $0.00126 |
| Haiku 4.5 | $0.00063 | $0.00063 |
Grade A, and why
mcp-debugger 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 4d 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 — 63 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.
Project Overview
MCP Debugger is a multi-language debugging plugin for Claude Code that leverages the Debug Adapter Protocol (DAP) to provide real debugging capabilities across Python, JavaScript/TypeScript, Go, and Rust. It enables setting breakpoints, stepping through execution, inspecting variables, and evaluating expressions in real debuggers (debugpy, vscode-js-debug, Delve, CodeLLDB).
Build Commands
npm run build # Compile TypeScript to bin/
npm run dev # Watch mode for development
npm test # Run vitest
npm run test:run # Run tests once (CI mode)
npm start # Run the compiled MCP server
npm run clean # Remove bin/ directory
Architecture
Layer Structure
- MCP Server (
src/server.ts) - Routes tool calls from Claude Code to handlers, exposes 18+ debugging tools - Session Manager (
src/session/session-manager.ts) - Central orchestrator managing debug session lifecycle and state - DAP Client (
src/dap/dap-client.ts) - Implements Debug Adapter Protocol, handles message parsing and adapter processes - Adapters (
src/adapters/) - Language-specific implementations for each debugger
Session State Machine
CREATED → INITIALIZING → READY → RUNNING ↔ PAUSED → TERMINATED (or ERROR)
Key Design Patterns
- Adapter Pattern: Each language has an
IDebugAdapterthat handles installation, configuration, and launch for its debugger - Registry Pattern:
AdapterRegistrymaps languages to adapter factories - Event-Driven:
EventEmitterused throughout; events bubble from DAP → Session Manager → MCP Server → Claude Code
Important Implementation Details
- Multi-Session DAP: vscode-js-debug uses reverse requests for child sessions connecting via TCP
- Async Launch: debugpy responds to launch only after
configurationDone()- uselaunchAsync()andwaitForLaunch() - Message Framing: DAP uses Content-Length headers with proper UTF-8 byte counting in
message-parser.ts - Breakpoint Queueing: Breakpoints set before debugging starts are stored and applied once adapter is ready
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.
- 4d ago First seen · 63 lines · 631 tokens per session scan A 473561017fea
mcp-debugger CLAUDE.md is an instructions file published in the GitHub repository bherbruck/mcp-debugger (2 stars, last pushed 5mo ago), licensed MIT. It adds 631 tokens to every session, about $0.0032 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 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).
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.
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 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.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.