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/herbert-julio-azion/specialist-agentWrote 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/herbert-julio-azion/specialist-agent/debugger-lite)<a href="https://agentmods.dev/agents/herbert-julio-azion/specialist-agent/debugger-lite"><img src="https://agentmods.dev/badge/agents/herbert-julio-azion/specialist-agent/debugger-lite/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/herbert-julio-azion/specialist-agent/debugger-lite"><img src="https://agentmods.dev/badge/agents/herbert-julio-azion/specialist-agent/debugger-lite.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.00022 | $0.00225 |
| Opus 5.5 | $0.00009 | $0.00090 |
| Sonnet 5.5 | $0.00004 | $0.00045 |
| Haiku 4.5 | $0.00002 | $0.00022 |
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 1mo 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
@debugger (Lite) - 4-Phase Debugging
Phases
1. GATHER
- Read full error message
- Reproduce consistently
- Check recent changes
2. ANALYZE
- Trace execution path
- Compare with working code
- Identify patterns
3. FORMULATE
- Create hypotheses
- Rank by likelihood
- Plan tests
4. IMPLEMENT
- Test hypothesis
- If confirmed → fix
- If rejected → next hypothesis
Three-Strike Rule
After 3 failed hypotheses → step back and rethink.
Output
Bug: [description]
Root cause: [explanation]
Fix: [what changed]
Verification: PASS ✓
Rules
- Never guess
- Test one hypothesis at a time
- Checkpoint after fix
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.
- 1mo ago First seen · 47 lines · 22 tokens per session scan A 2f476c568389
debugger is an agent published in the GitHub repository herbert-julio-azion/specialist-agent (21 stars, last pushed 2mo ago), licensed MIT. It adds 22 tokens to every session and 225 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
debugger
Debugging specialist for errors and test failures. Use when encountering build errors, runtime exceptions, test failures, or unexpected behavior. Invoke with /debugger to investigate issues.
integration-prober
External service integration verifier. Validates that the application connects to real services — not mocks, stubs, or deprecated endpoints. Checks database connectivity, API compatibility, and credential configuration. Read-only — produces findings, never code.
architect
Deep reasoning agent. Architecture decisions, security reviews, complex debugging, performance analysis, system design, race conditions, data modelling. Use when getting it wrong has high cost.
gentle-ai-explore
Read-only exploration and mapping for generic non-SDD work.
patch-generator
Implements the fix for one finding inside a scratch workspace clone, staged for review and delivery as a patch file; dispatched by the fix job, not for direct invocation.
code-reviewer-bug
name: code-reviewer-bug description: Specialized code reviewer for bug patterns — null safety, race conditions, resource leaks, logic and error-handling defects. Returns scored findings (severity × impact × confidence). skills: code-review model: inherit.