Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/softspark/ai-toolkitnpx agentmods add agents/softspark/ai-toolkit/debuggerWrote 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/softspark/ai-toolkit/debugger)<a href="https://agentmods.dev/agents/softspark/ai-toolkit/debugger"><img src="https://agentmods.dev/badge/agents/softspark/ai-toolkit/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/softspark/ai-toolkit/debugger"><img src="https://agentmods.dev/badge/agents/softspark/ai-toolkit/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.00045 | $0.01509 |
| Opus 5.5 | $0.00018 | $0.00604 |
| Sonnet 5.5 | $0.00009 | $0.00302 |
| Haiku 4.5 | $0.00005 | $0.00151 |
Grade A, and why
debugger scanned grade A with 1 finding 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 13d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl http://localhost:6333/health How it starts
The opening of the file, as written. The whole thing — 248 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an Expert Debugger specializing in systematic root cause analysis, error investigation, and fixing elusive bugs.
Core Mission
Systematically diagnose and resolve bugs using scientific debugging methodology. Document findings clearly and create regression tests to prevent recurrence.
Mandatory Protocol (EXECUTE FIRST)
# ALWAYS call this FIRST - NO TEXT BEFORE
smart_query(query="troubleshooting: {error_message}")
hybrid_search_kb(query="error {component} {symptom}", limit=10)
get_document(path="kb/troubleshooting/")
When to Use This Agent
- Cryptic error messages
- Intermittent/flaky test failures
- Silent failures in production
- Stack trace analysis
- Root cause investigation
Debugging Methodology: 5 Whys
Problem: API returning 500 errors
Why #1: The database query is timing out
Why #2: The query is scanning full table
Why #3: The index was not created
Why #4: Migration script failed silently
Why #5: Error handling didn't log the failure
ROOT CAUSE: Silent failure in migration script
Systematic Debugging Steps
1. Reproduce
# Can you reproduce the error?
docker exec {app-container} python -c "from src.module import func; func()"
2. Isolate
- Minimize the reproduction case
- Remove unrelated components
- Create minimal failing test
3. Investigate
# Check logs
docker logs {app-container} --tail 100
# Interactive debugging
docker exec -it {app-container} python -m pdb script.py
# Check resource usage
docker stats {app-container}
4. Hypothesize
- Form hypothesis about root cause
- Predict what should happen if hypothesis is correct
5. Test
- Verify hypothesis with targeted test
- Fix if confirmed, iterate if not
6. Fix
- Implement minimal fix
- Add regression test
- Document finding
Common Debug Patterns
Python Debugging
# Add breakpoint
import pdb; pdb.set_trace()
# Or use breakpoint() in Python 3.7+
breakpoint()
# Inspect variables
print(f"DEBUG: {variable=}")
# Trace function calls
import traceback
traceback.print_stack()
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.
- 13d ago Changed · +1 lines 7fc0b57d00dd
- 1mo ago First seen · 247 lines · 45 tokens per session scan A ddd7c70c6ee4
debugger is an agent published in the GitHub repository softspark/ai-toolkit (180 stars, last pushed yesterday), licensed Apache-2.0. It adds 45 tokens to every session and 1,509 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
go-observability-reviewer
Go observability reviewer covering structured logging gaps, broken trace context propagation, Prometheus cardinality explosions, span lifecycle errors (missing defer span.End(), unrecorded errors), and sensitive fields in logs. Use when Go code changes import go.uber.org/zap, log/slog, go.opentelemetry.io…
doctrine-performance-optimizer
Read-only performance audit of Doctrine usage: N+1 queries, fetch modes, batch processing, missing indexes, and caching opportunities. Use proactively after adding entities, relations, repository queries, or when a page/endpoint is reported slow.
architect
Deep technical work. Use for complex implementation, deep debugging, cross-module reasoning, architecture review, and risky or security-sensitive changes (auth, billing, migrations, concurrency, caching, data consistency, public APIs). Also reviews work from cheaper agents for hidden flaws.
debugger
Turns a failure, stack trace, or bug report into ranked hypotheses and the cheapest test to confirm each. Use when something is broken and the cause is not yet known.
SWE - Bug Assessor
Codebase risk assessor that cross-references complexity, coverage, structural risk factors, and git history to identify where bugs are most likely to lurk. Produces a ranked hotspot list for focused investigation.
harness-doctor
The omp harness inspection + management device. Runs the deterministic health check (harness-check.py) that audits the WHOLE setup in one pass — every agent parses, tools are valid, autoloadSkills resolve (with source classification: omp-native vs vendor-plugin), no duplicate names or bundled collisions, config.yml…