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/christopherlouet/claude-base/dev-debuggit clone --depth 1 https://github.com/christopherlouet/claude-baseWhat 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.00027 | $0.00315 |
| Opus 5 | $0.00014 | $0.00158 |
| Sonnet 5 | $0.00005 | $0.00063 |
| Haiku 4.5 | $0.00003 | $0.00032 |
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 yesterday.
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.
- yesterday 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 2d ago), licensed MIT. It adds 27 tokens to every session and 315 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-31.
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.
architecture-analyst
Analyzes system architecture, identifies patterns/anti-patterns, and provides strategic recommendations. Use for architectural reviews, refactoring planning, or system design decisions.
blockchain-developer
Solidity, smart contracts, Web3, EVM, DeFi protocols, and blockchain development specialist. Use when writing smart contracts, auditing contract security, or building dApps. Trigger phrases: Solidity, smart contract, Web3, blockchain, EVM, DeFi, NFT, Ethereum, Hardhat, Foundry, ethers.js, wagmi.
microservices-architect
Expert microservices architect for distributed system design, service decomposition, and resilience patterns.
adapter_grok
Grok is an eagerly registered stock-TUI adapter. RimZ launches grok, installs passive global hooks in ${GROKHOME:-/.grok}/hooks/rimz.json, and enriches each session from its durable updates.jsonl, summary.json, signals.json, and optional events.jsonl files. ACP and provider-private billing APIs stay outside this…