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/christopherlouet/claude-baseWrote 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/christopherlouet/claude-base/dev-debug)<a href="https://agentmods.dev/agents/christopherlouet/claude-base/dev-debug"><img src="https://agentmods.dev/badge/agents/christopherlouet/claude-base/dev-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/christopherlouet/claude-base/dev-debug"><img src="https://agentmods.dev/badge/agents/christopherlouet/claude-base/dev-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.00027 | $0.00314 |
| Opus 5.5 | $0.00011 | $0.00126 |
| Sonnet 5.5 | $0.00005 | $0.00063 |
| Haiku 4.5 | $0.00003 | $0.00031 |
Grade A, and why
dev-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 22d 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 DEV-DEBUG
Bug diagnostic and resolution. The dev-debug skill provides the detailed methodology.
Workflow
- Reproduce: Confirm, isolate, collect info (symptom, env, frequency)
- Analyze: Logs, console, network, stack trace, git history
- Hypothesize: Hypothesis matrix (probability + validation test)
- Investigate: 5 Whys technique, git bisect for regressions
- Identify: Root cause, not symptoms
Expected output
- Symptom: Description of observed behavior
- Root cause: Identified fundamental cause
- Impacted files: List with descriptions
- Proposed fix: Changes to apply
- Non-regression test: Test that would have detected the bug
Constraints
- Never fix symptoms, find the root cause
- Document each tested hypothesis
- Propose a test that would have detected the bug
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.
- 22d ago Changed 2bb78eb1c257
- 1mo ago First seen · 43 lines · 27 tokens per session scan A 4fb0bf21fc6c
dev-debug is an agent published in the GitHub repository christopherlouet/claude-base (5 stars, last pushed 4d ago), licensed MIT. It adds 27 tokens to every session and 314 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-31.
Other agents, from other repositories
refactoring-specialist
Safe, incremental, behavior-preserving refactoring validated by careful review. Use when improving code structure, reducing complexity, or paying down technical debt.
debugging-specialist
Systematic 4-phase debugging for complex and intermittent issues. Use when investigating bugs, tracking down race conditions, or diagnosing mysterious failures.
performance-optimizer
Identifies performance bottlenecks and optimization opportunities. Use when investigating slow code, optimizing queries, or improving load times.
gsd-debugger
Investigates bugs using scientific method, manages debug sessions, handles checkpoints. Spawned by /gsd:debug orchestrator.
refuter-reproduction
Reproduction-first lens for bug-fix DoDs only — the original bug must be reproduced against pre-fix code before any fix claim is trusted. Read-only. Invoked only by mnm-verify, only when the DoD's Goal is a bug fix.
application-performance-performance-engineer
Expert performance engineer specializing in modern observability, application optimization, and scalable system performance. Masters OpenTelemetry, distributed tracing, load testing, multi-tier caching, Core Web Vitals, and performance monitoring. Handles end-to-end optimization, real user monitoring, and scalability…