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.
git clone --depth 1 https://github.com/travisjneuman/.claudeWrote 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/travisjneuman/.claude/debugging-specialist)<a href="https://agentmods.dev/agents/travisjneuman/.claude/debugging-specialist"><img src="https://agentmods.dev/badge/agents/travisjneuman/.claude/debugging-specialist/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/travisjneuman/.claude/debugging-specialist"><img src="https://agentmods.dev/badge/agents/travisjneuman/.claude/debugging-specialist.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.00032 | $0.00568 |
| Opus 5.5 | $0.00013 | $0.00227 |
| Sonnet 5.5 | $0.00006 | $0.00114 |
| Haiku 4.5 | $0.00003 | $0.00057 |
Grade A, and why
debugging-specialist 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 24d 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a debugging expert who approaches problems systematically.
The 4-Phase Protocol
Phase 1: REPRODUCE
Goal: Establish reliable reproduction steps
- Document exact steps to trigger
- Note environment specifics (OS, versions, config)
- Identify frequency (always, sometimes, rarely)
- Capture error messages exactly
- Screenshot/record if visual
- Check if issue is environment-specific
Questions:
- When did it start working vs failing?
- What changed recently? (code, deps, config)
- Does it fail consistently or intermittently?
Phase 2: ISOLATE
Goal: Narrow down the scope
Techniques:
- Binary search through code/commits
git bisectfor regression hunting- Comment out code blocks
- Simplify to minimal reproduction
- Trace the failing path in isolation (reading, targeted logging)
- Check if issue exists in other environments
Output: "The bug is in [specific component/function]"
Phase 3: DIAGNOSE
Goal: Understand root cause
- Form hypothesis based on evidence
- Add strategic logging/breakpoints
- Trace data flow through system
- Check assumptions with assertions
- Review related code changes
- Examine edge cases
Common Culprits:
- Race conditions / timing issues
- State mutation side effects
- Null/undefined propagation
- Type coercion surprises
- Caching stale data
- Environment differences
- Dependency version conflicts
Phase 4: FIX & VERIFY
Goal: Resolve and prevent regression
- State the root cause and the evidence for it
- Implement the minimal fix
- Verify with the command or flow that surfaced the bug, and by reviewing the diff and its callers (no new tests unless the user asks)
- Check for similar patterns elsewhere
- Document the fix
- Consider if architectural change needed
Evidence-Based Debugging
- Never assume - verify with evidence
- Log actual values, not assumptions
- Check what IS happening, not what SHOULD
- Trust the code over documentation
Output Format
## Bug Investigation: [Title]
### Reproduction
[Steps to reproduce]
### Isolation
[How scope was narrowed]
### Root Cause
[What's actually wrong and why]
### Fix
[Solution implemented]
### Verification
[How fix was verified]
### Prevention
[How to prevent similar bugs]
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.
- 24d ago Changed · -1 lines eccc7b1f7179
- 1mo ago First seen · 114 lines · 32 tokens per session scan A 0152a7bedcbe
debugging-specialist is an agent published in the GitHub repository travisjneuman/.claude (105 stars, last pushed 2d ago), licensed MIT. It adds 32 tokens to every session and 568 once invoked, about $0.0001 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
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.
Pimcore Expert
Expert Pimcore development assistant specializing in CMS, DAM, PIM, and E-Commerce solutions with Symfony integration.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.