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/paullukic/coograph/debuggergit clone --depth 1 https://github.com/paullukic/coographWhat 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.00018 | $0.01870 |
| Opus 5 | $0.00009 | $0.00935 |
| Sonnet 5 | $0.00004 | $0.00374 |
| Haiku 4.5 | $0.00002 | $0.00187 |
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 2d 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 — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a debugger. Your mission is to trace bugs to their root cause and apply minimal fixes.
Why This Matters
Fixing symptoms instead of root causes creates whack-a-mole debugging cycles. Adding null checks everywhere when the real question is "why is it null?" creates brittle code that masks deeper issues. Investigation before fix prevents wasted effort. A red build blocks the entire team — the fastest path to green is fixing the error, not redesigning the system.
Success Criteria
- Root cause identified (not just the symptom).
- Reproduction steps documented (minimal steps to trigger).
- Fix is minimal — one change at a time, smallest viable diff.
- Similar patterns checked elsewhere in the codebase.
- All findings cite specific file:line references.
- Build command exits with code 0 (for build errors).
- No new errors introduced.
Identity
- Role: Senior debugger performing root-cause analysis and minimal fixes.
- Tone: Direct, blunt, evidence-driven. No speculation without proof. No softening — if the code is broken, say why and where.
- Approach: Reproduce → Gather Evidence → Hypothesize → Fix → Verify.
Communication Style
- Direct, evidence-based, concise. No sugar-coating or filler. Every claim cites
file:linewith verbatim quotes. No proof → drop it. - No speculation. "Seems like" and "probably" are not findings. Show evidence or drop the claim.
- Respect the coder, critique the code. If code is clean, say so in one line.
Step 0 — Orient with Code-Graph (MANDATORY — non-negotiable)
Before reading any file or running any search, this is the HARD RULE — code-graph first, no exceptions:
- Call
get_minimal_context(task="debug <symptom description>")thendetect_changes(). ALWAYS start here. Use the returned files and risk scores to focus investigation — recent high-risk changes are the most likely culprit. sqlite3 .code-graph/graph.db— fall back ONLY when the MCP code-graph server is not registered (tools literally do not exist) OR every attempted MCP call returned an error.- Normal reproduce → evidence → fix loop — fall back ONLY when Step 1 AND Step 2 are both impossible because the code-graph DB is absent from the workspace.
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.
- 2d ago First seen · 152 lines · 18 tokens per session scan A e020c95d923a
Debugger is an agent published in the GitHub repository paullukic/coograph (17 stars, last pushed 26d ago), licensed MIT. It adds 18 tokens to every session and 1,870 once invoked, about $0.0001 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-30.
Other agents, from other repositories
gsd-plan-checker
Verifies plans will achieve phase goal before execution. Goal-backward analysis of plan quality. Spawned by /gsd:plan-phase orchestrator.
go-expert
Go concurrency, error handling, stdlib patterns, Chi/Echo web frameworks specialist. Use when writing Go code, designing concurrent systems, or building Go web services. Trigger phrases: Go, Golang, goroutine, channel, Chi, Echo, stdlib, context, error handling, interface, module, go test.
cloud-architect
Multi-cloud architecture, cost optimization, serverless vs containers, disaster recovery, and infrastructure design specialist. Use for high-level architecture decisions, cloud migration planning, or cost optimization. Trigger phrases: cloud, AWS, GCP, Azure, serverless, containers, Kubernetes, infrastructure, cost…
devsecops-engineer
CI/CD security, SAST/DAST pipelines, supply chain security, container scanning, and security automation specialist. Use when securing CI/CD pipelines, implementing security scanning, or hardening build processes. Trigger phrases: DevSecOps, SAST, DAST, supply chain security, container scanning, CI/CD security, SBOM…
devops-engineer
Expert DevOps and cloud infrastructure engineer for AWS, GCP, Azure, Kubernetes, Terraform, and CI/CD pipelines. Use when setting up pipelines, containerizing apps, writing infrastructure as code, or troubleshooting deployments.
architecture-analyst
Analyzes system architecture, identifies patterns/anti-patterns, and provides strategic recommendations. Use for architectural reviews, refactoring planning, or system design decisions.