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/ai-debugger-inc/aidb/claude-mdgit clone --depth 1 https://github.com/ai-debugger-inc/aidbWrote 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/ai-debugger-inc/aidb/claude-md)<a href="https://agentmods.dev/instructions/ai-debugger-inc/aidb/claude-md"><img src="https://agentmods.dev/badge/instructions/ai-debugger-inc/aidb/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.01596 | $0.01596 |
| Opus 5 | $0.00798 | $0.00798 |
| Sonnet 5 | $0.00319 | $0.00319 |
| Haiku 4.5 | $0.00160 | $0.00160 |
Grade A, and why
aidb 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Debugger (aidb) - Claude Code Context
Project Overview
AI Debugger (aidb) is a lightweight, language-agnostic Python API that enables AI systems to programmatically control and introspect live debugging sessions through the Debug Adapter Protocol (DAP). It serves as an ideal Model Context Protocol (MCP) tool for AI-assisted debugging workflows.
The debugger interface is intended to function at a human cadence, not a typical, super-fast API. For example:
- If you want to inspect runtime state in a program that executes quickly, you must set a breakpoint when you start the debug session. If you need to set a conditional breakpoint, you must do so before starting the debug session.
- If you want to perform introspection on the state, you must execute the operations on a paused program that fetch whatever is needed, e.g. local variables or a stack frame.
- If you want to advance a line, that is a single operation. To skip multiple lines, you must execute multiple operations, just like a human using a debugger.
- If you want to use your
launch.jsonfile, you can.
User Profile: Developers building debugging tools + AI agents using MCP for code debugging workflows.
Project Components
Core Debugger: aidb/ - Language-agnostic debugging API, adapters (Python/JavaScript/Java), session management
MCP Integration: aidb_mcp/ - MCP server exposing 12 debugging tools to AI agents
Developer Tools: aidb_cli/ - CLI for testing orchestration, Docker management, adapter builds
Shared Libraries: aidb_common/ (config, validation, paths), aidb_logging/ (structured logging)
Architecture Overview
AI Debugger is built on a layered architecture that provides language-agnostic debugging capabilities:
- MCP Layer (
aidb_mcp/): Model Context Protocol server exposing 12 agent-optimized debugging tools - Service Layer (
aidb/service/): Stateless debugging operations via DebugService with sub-services for execution, stepping, breakpoints, variables, and stack inspection - Session Layer (
aidb/session/): Core session orchestration, state management, and lifecycle control - Adapter Layer (
aidb/adapters/): Language-specific debug adapters (Python, JavaScript, Java) - DAP Client Layer (
aidb/dap/client/): Debug Adapter Protocol client implementation - Protocol Layer (
aidb/dap/protocol/): Fully-typed DAP specification (authoritative reference)
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 · 137 lines · 1,596 tokens per session scan A fa9eb7093e66
aidb CLAUDE.md is an instructions file published in the GitHub repository ai-debugger-inc/aidb (21 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 1,596 tokens to every session, about $0.0080 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-30.
Other instructions, from other repositories
mem0 AGENTS.md
AGENTS.md instructions for mem0ai/mem0, covering agents.md, do not, where to look, repository map and setup.
ollama AGENTS.md
AGENTS.md instructions for ollama/ollama, covering agents.md and building.
ollama CLAUDE.md
Claude Code instructions for ollama/ollama: See AGENTS.md for the shared agent instructions for this repository.
pydantic-ai AGENTS.md
AGENTS.md instructions for pydantic/pydantic-ai, covering your primary responsibility is to the project and its users, gathering context on the task, ensuring the task is ready for implementation, philosophy and requirements of all contributions.
parlant CLAUDE.md
Instructions for emcie-co/parlant: This is the main repo of Parlant (https://parlant.io).
dstack AGENTS.md
AGENTS.md instructions for dstackai/dstack, covering repository guidelines, project structure & module organization, build, test, and development commands, coding style & naming conventions and testing guidelines.