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 commands/christopherlouet/claude-base/dev-debuggit 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/commands/christopherlouet/claude-base/dev-debug)<a href="https://agentmods.dev/commands/christopherlouet/claude-base/dev-debug"><img src="https://agentmods.dev/badge/commands/christopherlouet/claude-base/dev-debug.svg" alt="Measured on agentmods" 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.00372 |
| Opus 5 | $0.00000 | $0.00186 |
| Sonnet 5 | $0.00000 | $0.00074 |
| Haiku 4.5 | $0.00000 | $0.00037 |
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 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.
What it actually says
Agent DEBUG
Methodical and systematic bug diagnostic and resolution.
Problem to analyze
$ARGUMENTS
Goal
Identify the root cause of a bug and fix it definitively, adding protections to prevent its recurrence.
Use the dev-debug skill for the detailed methodology (4 phases: Observation, Hypotheses, Investigation, Verification).
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
- Fix: Minimal fix at the root cause
- Prevent: Regression test
Expected output
Diagnostic
- Symptom: Description of the observed behavior
- Root cause: Identified fundamental cause
- Impacted files: List with descriptions
- Culprit commit: Hash (if found via bisect)
Solution
- Applied fix: Description of the correction
- Added test: Regression test
- Verification: Bug fixed, tests pass, no side effects
Related agents
| Agent | When to use it |
|---|---|
/work:work-explore |
Understand the code context |
/dev:dev-tdd |
Add regression tests |
/work:work-commit |
Commit the fix |
IMPORTANT: Never fix symptoms. Always find the root cause.
YOU MUST add a test that would have caught this bug.
YOU MUST document the root cause to prevent recurrence.
Think hard about why this bug was not detected earlier.
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 · 54 lines · 0 tokens per session scan A fdb40827d3ce
dev-debug is a command published in the GitHub repository christopherlouet/claude-base (5 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 372 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-09-03.
Other commands, from other repositories
e2e
Create and run E2E tests across web, mobile, and desktop with auto-detection and CLI-first toolchains.
clean
Identify and safely remove dead code with test verification.
fix
Auto-detect and fix LSP errors, linting issues, and type errors.
loop
Iteratively fix issues until all resolved or max iterations reached.
run
Implement SPEC requirements using DDD/TDD methodology.
test-plan
Generate a test strategy document — test matrix, coverage goals, and test pyramid allocation for the current project.