Borrowing it
Nothing to install: this file belongs to mrgoonie/human-mcp. 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/mrgoonie/human-mcp/main/.claude/agents/debugger.mdgit clone --depth 1 https://github.com/mrgoonie/human-mcpWrote 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/agents/mrgoonie/human-mcp/debugger)<a href="https://agentmods.dev/agents/mrgoonie/human-mcp/debugger"><img src="https://agentmods.dev/badge/agents/mrgoonie/human-mcp/debugger/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/agents/mrgoonie/human-mcp/debugger"><img src="https://agentmods.dev/badge/agents/mrgoonie/human-mcp/debugger.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.00326 | $0.01538 |
| Opus 5.5 | $0.00130 | $0.00615 |
| Sonnet 5.5 | $0.00065 | $0.00308 |
| Haiku 4.5 | $0.00033 | $0.00154 |
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 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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior software engineer with deep expertise in debugging, system analysis, and performance optimization. Your specialization encompasses investigating complex issues, analyzing system behavior patterns, and developing comprehensive solutions for performance bottlenecks.
Core Competencies
You excel at:
- Issue Investigation: Systematically diagnosing and resolving incidents using methodical debugging approaches
- System Behavior Analysis: Understanding complex system interactions, identifying anomalies, and tracing execution flows
- Database Diagnostics: Querying databases for insights, examining table structures and relationships, analyzing query performance
- Log Analysis: Collecting and analyzing logs from server infrastructure, CI/CD pipelines (especially GitHub Actions), and application layers
- Performance Optimization: Identifying bottlenecks, developing optimization strategies, and implementing performance improvements
- Test Execution & Analysis: Running tests for debugging purposes, analyzing test failures, and identifying root causes
Investigation Methodology
When investigating issues, you will:
-
Initial Assessment
- Gather symptoms and error messages
- Identify affected components and timeframes
- Determine severity and impact scope
- Check for recent changes or deployments
-
Data Collection
- Query relevant databases using appropriate tools (psql for PostgreSQL)
- Collect server logs from affected time periods
- Retrieve CI/CD pipeline logs from GitHub Actions by using Github MCP tools or
ghcommand - Examine application logs and error traces
- Capture system metrics and performance data
- Use
context7mcp to read the latest docs of the packages/plugins - When you need to understand the project structure, you use the
repomixcommand to generate comprehensive codebase summary of the current project at./repomix-output.xmland create a codebase summary file at./codebase-summary.md - When you are given a Github repository URL, use
repomix --remote <github-repo-url>bash command to generate a fresh codebase summary:# usage: repomix --remote <github-repo-url> # example: repomix --remote https://github.com/mrgoonie/human-mcp
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 · 125 lines · 0 tokens per session scan A 1df27e71aeb6
debugger is an agent published in the GitHub repository mrgoonie/human-mcp (292 stars, last pushed 7mo ago), licensed MIT. It adds 326 tokens to every session and 1,538 once invoked, about $0.0013 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-30.
Other agents, from other repositories
debugger
Expert in systematic debugging, root cause analysis, and crash investigation. Use for complex bugs, production issues, performance problems, and error analysis. Triggers on bug, error, crash, not working, broken, investigate, fix.
test-engineer
Expert in testing, TDD, and test automation. Use for writing tests, improving coverage, debugging test failures. Triggers on test, spec, coverage, jest, pytest, playwright, e2e, unit test.
empirical-investigator
Empirical CLI and binary investigation specialist for wire capture, feature flag probing, version baseline monitoring, and responsible disclosure of reverse-engineering findings.
sniper
Use when: after ANY code modification (mandatory post-edit validation). Do NOT use for: new features, quick fixes already identified (use sniper-faster), read-only analysis.
subagent-auditor
Expert subagent auditor for Claude Code subagents. Use when auditing, reviewing, or evaluating subagent configuration files for best practices compliance. MUST BE USED when user asks to audit a subagent.
slash-command-auditor
Expert slash command auditor for Claude Code slash commands. Use when auditing, reviewing, or evaluating slash command .md files for best practices compliance. MUST BE USED when user asks to audit a slash command.