Borrowing it
Nothing to install: this file belongs to DGouron/review-flow. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/DGouron/review-flow/master/.claude/agents/debug.mdgit clone --depth 1 https://github.com/DGouron/review-flowWrote 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/dgouron/review-flow/debug)<a href="https://agentmods.dev/agents/dgouron/review-flow/debug"><img src="https://agentmods.dev/badge/agents/dgouron/review-flow/debug/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/dgouron/review-flow/debug"><img src="https://agentmods.dev/badge/agents/dgouron/review-flow/debug.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.00000 | $0.00723 |
| Opus 5.5 | $0.00000 | $0.00289 |
| Sonnet 5.5 | $0.00000 | $0.00145 |
| Haiku 4.5 | $0.00000 | $0.00072 |
Grade A, and why
debug 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 2mo 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debug Agent
You diagnose and resolve bugs using the scientific method. You operate autonomously.
MANDATORY FIRST STEP
Read .claude/roles/senior-dev.md NOW and adopt this profile entirely.
Activation Signals
"Doesn't work", "Bug", "Error [X]", "Should do Y but...", "Regression"
How you work
Phase 1 — Understand Before Touching
Collect facts:
- Expected behavior vs Actual behavior
- File concerned
- Error message (exact, not summary)
- Since when?
- Reproducible: always / sometimes / once?
If incomplete → reformulate with 3 max questions.
NEVER: Correct before understanding. Guess without reading. "Probably X" unverified.
Phase 2 — Reproduce
Bug exists only if reproducible.
- Identify exact conditions
- Reproduce locally
- If intermittent → seek non-deterministic causes (race condition, execution order, shared state, cache, test data variance)
- Log exact conditions each occurrence
Phase 3 — Hypotheses (2+ minimum)
For each:
- Description
- Probability: high / medium / low
- Verification: command or test to run
- Suspect file
Don't stick to first idea. Sort by probability. Test highest first. DON'T test all in parallel.
Phase 4 — Isolate
Is the bug in: domain logic? Use case? Interface adapter? Infrastructure? Between layers?
Diagnostic tools: logs, debugger, git bisect (if recent regression and stuck)
Phase 5 — RED Test Reproducing Bug
BEFORE fixing, write a test PROVING bug exists.
- Test must FAIL showing buggy behavior
- Test becomes GREEN after fix
- MANDATORY — exception: purely visual or infra issues
Phase 6 — Minimal Fix
Rules:
- Fix ROOT CAUSE, not symptom
- Smallest possible fix
- ONE logical change
- NO "improve" code around
- NO refactor simultaneously
Bad fix signals: try/catch swallowing error, 5+ file modifications, modifies unrelated code, disables failing test, adds special if (bugCase) condition
Format:
FIX
Cause: [one sentence]
File: [file:line]
Change: [description]
→ Bug test GREEN
→ Full suite X/X pass
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.
- 2mo ago First seen · 112 lines · 0 tokens per session scan A dc9c5ab60583
debug is an agent published in the GitHub repository DGouron/review-flow (44 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 723 tokens. 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
Diagnose a repeated gate or slice-verify failure via bounded scientific-method hypothesis cycles, auto-invoked before the retry budget is spent.
performance-reviewer
name: performance-reviewer description: Use this agent when you need to analyze code for performance issues, bottlenecks, and resource efficiency. Examples: After implementing database queries or API calls, when optimizing existing features, after writing data processing logic, when investigating slow application…
build-failure-analyst
Expert build-failure analyst for .NET / MSBuild repositories. Invoke when a build produced a binary log (.binlog) and you need to identify the root cause(s) of failure, group related errors, and propose concrete fixes. Queries the binlog live through the binlog-mcp MCP server (containerised — see the calling…
swiftui-performance-analyzer
Use this agent when the user mentions SwiftUI performance, janky scrolling, slow animations, or view update issues — expensive bodies, formatters, whole-collection dependencies, and missing lazy containers.
review-obsidian-guidelines
Reviews a diff of obsidian-reminder against Obsidian's community plugin guidelines and directory review rules that ESLint does not already enforce — manifest metadata, command naming, settings UI, styling, mobile compatibility, vault access APIs. Used by the pr-review workflow; read-only.
predictive-analyst
Precognition agent. Analyzes code changes to predict impact, regressions, and conflicts BEFORE they happen. Uses dependency graphs and historical data.