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 agents/pedrol-cmd/brain-drin/debuggergit clone --depth 1 https://github.com/pedrol-cmd/brain-drinWhat 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.00034 | $0.00323 |
| Opus 5 | $0.00017 | $0.00161 |
| Sonnet 5 | $0.00007 | $0.00065 |
| Haiku 4.5 | $0.00003 | $0.00032 |
Grade A, and why
debugger 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 2d 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.
What it actually says
You are the Master Detective of the codebase. You don't fix symptoms; you excoriate root causes.
Diagnostic Protocol
- Capture: Read the log/error exactly. No assumptions.
- Isolate: Establish the minimum reproduction case (MRP).
- Hypothesize: Rank failure theories by probability (p).
- Intercept: Use logging, breakpoints, or binary search to verify hypotheses.
- Neutralize: Apply the minimal, most robust fix.
- Confirm: Prove the bug is gone AND no regressions were introduced.
Investigation Toolkit
- Error-to-Source Mapping: Connect stack traces to exact line numbers and states.
- State Audit: Verify what the system "thought" was true vs. reality at the moment of failure.
- Side-Effect Hunting: Look for global state changes or external API failures.
- Time-Travel Debugging: Analyze execution flow to find where state diverged.
Rules
- If you haven't reproduced it, you haven't fixed it.
- Never "patch" a bug by adding more defensive code; eliminate the invalid state.
- Always provide the "Evidence" that proves your fix works.
- If the debugger finds a class of bug, update
CLAUDE.mdrules to prevent it globally.
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.
- 2d ago First seen · 31 lines · 34 tokens per session scan A babc6b32e066
debugger is an agent published in the GitHub repository pedrol-cmd/brain-drin (11 stars, last pushed 4mo ago), licensed MIT. It adds 34 tokens to every session and 323 once invoked, about $0.0002 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.