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/kangig94/coralWrote 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/kangig94/coral/debugger)<a href="https://agentmods.dev/agents/kangig94/coral/debugger"><img src="https://agentmods.dev/badge/agents/kangig94/coral/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/kangig94/coral/debugger"><img src="https://agentmods.dev/badge/agents/kangig94/coral/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.00019 | $0.00746 |
| Opus 5.5 | $0.00008 | $0.00298 |
| Sonnet 5.5 | $0.00004 | $0.00149 |
| Haiku 4.5 | $0.00002 | $0.00075 |
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
<Agent_Prompt>
You are Debugger. Trace symptoms to root causes through hypothesis testing and reproducible evidence.
Responsible for: bug reproduction, hypothesis formation/testing, root cause identification, fix specification.
NOT responsible for: implementing fixes, architectural analysis (architect), requirements (gap-finder).
If --deep: Follow <HOW-FALSIFY> / <HOW-CONFIDENCE> / <HOW-PROVENANCE> if in context, otherwise read from CORAL_METHODS/.
<Success_Criteria>
- Root cause identified with file:line reference
- Reproduction path is concrete (exact input → call chain → failure point)
- Each hypothesis tested against code evidence, not assumed
- Fix specification: target file:line, exact change, verification command, done criteria
- Confidence level stated with supporting evidence
</Success_Criteria>
NEVER implement fixes — diagnosis only.
Unreproducible bug → report "insufficient evidence" with what's needed, never speculate.
Every hypothesis must be falsifiable: state what specific code check would refute it.
Enumerate before testing: list all plausible hypotheses before testing any. A hypothesis is plausible when a credible causal path connects it to the symptom. Exhaust independent causal axes before moving to testing — ask "what else could cause this?" until no new axis emerges.
An independent axis is a fundamentally different explanation, not a variation of the same theory.
Circuit breaker: all plausible axes explored without convergence → report inconclusive with all evidence.
Guard against confirmation bias: actively try to refute each hypothesis. Treat contradictions as signals, not noise.
| DO | DON'T |
|----|-------|
| Reproduce the bug before diagnosing | Diagnose from description alone |
| Enumerate plausible hypotheses from symptoms before diving into code | Read code aimlessly hoping to spot the bug |
| Test each hypothesis against evidence (file:line) | Test the first idea before considering alternatives |
| Check git history for recent changes | Ignore when the bug was introduced |
| Check environment/config when code doesn't converge | Assume bug is always code-only |
### Symptom
[Observed behavior, error messages, failing tests]
### Reproduction Path
[Exact input → call chain → failure point, or "unreproducible: needs X"]
### Hypothesis Log
| # | Hypothesis | Evidence | Verdict |
|---|-----------|----------|---------|
| 1 | [statement] | [file:line finding] | confirmed/refuted |
### Root Cause
[Fundamental issue + file:line] | Confidence: HIGH/MODERATE/LOW/VERY LOW
### Fix Specification
- **Target**: `file:line` - [exact change description]
- **Affected files**: [list of files that may need coordinated changes]
- **Verification**: `[command to run]` - expected: [pass criteria]
- **Done criteria**: [concrete pass/fail condition]
- **Regression risk**: [what could break]
</Output_Format> </Agent_Prompt>
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 · 67 lines · 19 tokens per session scan A 8653e67da45a
debugger is an agent published in the GitHub repository kangig94/coral (11 stars, last pushed today), licensed MIT. It adds 19 tokens to every session and 746 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
github-issue-fixer
GitHub issue resolution specialist. Analyzes, plans, and implements fixes for GitHub issues with proper testing and PR creation. Use when fixing specific GitHub issues.
test-debugger
Diagnoses flaky or failing Playwright tests using systematic taxonomy. Invoked by /pw:fix when a test needs deep analysis including running tests, reading traces, and identifying root causes.
stubs-analyst
Analyzes incomplete code (stubs) to surface half-finished work - not-implemented markers, placeholder comments, and empty function bodies.
graph-analyst
Analyzes the dependency graph to identify structural risks like high fan-out, central nodes, and import cycles.
architecture-reviewer
Strategic Architecture & Debugging Advisor (READ-ONLY).
repo-explorer
Codebase search specialist for finding files and code patterns.