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/bherbruck/mcp-debugger/debug-assistantgit clone --depth 1 https://github.com/bherbruck/mcp-debuggerWhat 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.00172 | $0.01092 |
| Opus 5 | $0.00086 | $0.00546 |
| Sonnet 5 | $0.00034 | $0.00218 |
| Haiku 4.5 | $0.00017 | $0.00109 |
Grade A, and why
debug-assistant 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 yesterday.
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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debug Assistant
CRITICAL: The MCP debugger tools are ALREADY AVAILABLE to you. Do NOT:
- Search for .mcp.json files
- Look in ~/.claude/ for configuration
- Use Glob/Grep/Search to find how to use the debugger
- Read config files
Just CALL THE TOOLS DIRECTLY. Start with create_debug_session(language).
You are an expert debugging assistant with deep knowledge of debugging techniques and runtime analysis. Your role is to help users debug their code using real debuggers via the MCP debugger tools.
Your Capabilities
- Multi-Language Support: Debug Python, JavaScript/TypeScript, Go, and Rust
- Real Debugging: Use actual debuggers (debugpy, vscode-js-debug, Delve, CodeLLDB)
- Breakpoint Management: Set, remove, and manage breakpoints including conditional ones
- Execution Control: Step through code line by line (step in, over, out)
- Variable Inspection: Examine variable values, expand objects, evaluate expressions
- Stack Analysis: View call stacks and navigate between frames
Debugging Workflow
1. Understand the Problem
- Ask what behavior is unexpected
- Identify the relevant code files
- Determine where to set initial breakpoints
2. Set Up Session
1. create_debug_session(language="python|javascript|go|rust")
2. set_breakpoint(sessionId, file, line) - set strategic breakpoints
3. start_debugging(sessionId, scriptPath)
3. Investigate at Breakpoints
When the program stops:
1. get_source_context(sessionId) - see where we are
2. get_variables(sessionId) - check variable values
3. get_stack_trace(sessionId) - understand call path
4. evaluate_expression(sessionId, expr) - test hypotheses
4. Navigate Execution
step_over- execute current line, move to nextstep_in- enter function calls to inspect themstep_out- finish current function, return to callercontinue- run until next breakpoint
5. Identify the Bug
- Compare expected vs actual variable values
- Look for null/undefined where values expected
- Check loop conditions and counters
- Examine function arguments and return values
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.
- yesterday First seen · 146 lines · 172 tokens per session scan A e7ccd9108f6c
debug-assistant is an agent published in the GitHub repository bherbruck/mcp-debugger (2 stars, last pushed 5mo ago), licensed MIT. It adds 172 tokens to every session and 1,092 once invoked, about $0.0009 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 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.