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/aawwcc/ape/debuggergit clone --depth 1 https://github.com/AAWWCC/apeWhat 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.00007 | $0.00190 |
| Opus 5 | $0.00003 | $0.00095 |
| Sonnet 5 | $0.00001 | $0.00038 |
| Haiku 4.5 | $0.00001 | $0.00019 |
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 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.
Copies of this mod
8 near-identical copies found in the catalogue:
- spike-researcher — 95% identical, 8 lines differ
- preflight-analyst — 94% identical, 6 lines differ
- plan-checker — 92% identical, 6 lines differ
- security-reviewer — 91% identical, 8 lines differ
- plan-judge — 89% identical, 6 lines differ
- test-writer — 88% identical, 8 lines differ
- implementer — 88% identical, 8 lines differ
- planner — 86% identical, 6 lines differ
What it actually says
Read ${CLAUDE_PLUGIN_ROOT}/prompts/common.md and ${CLAUDE_PLUGIN_ROOT}/prompts/debugger.md,
then execute the supplied StageTicket exactly.
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 · 10 lines · 7 tokens per session scan A 9104526f9f74
debugger is an agent published in the GitHub repository AAWWCC/ape (0 stars, last pushed yesterday), licensed MIT. It adds 7 tokens to every session and 190 once invoked, about $0.0000 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
docs-specialist
Expert technical writer focused on clear, complete, and continuously accurate documentation. Audits, writes, and improves all project docs from README to API references.
gem-mobile-tester
Mobile E2E testing: Detox, Maestro, iOS/Android simulators.
integration-reviewer
Runtime integration validator — read-only. Validates service connection parameters, async/sync consistency, env var completeness, library API correctness, and OTEL pipeline completeness. Triggered during /plan-validate when new services, libraries, or observability config are in scope.
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
mathodology-problem-analyst
Use for contest problem decomposition, scoring criteria, constraints, variables, assumptions, and deliverable mapping.
refactor
Use when code has grown complex, has duplication, violates patterns, or needs restructuring - from code smells to architecture-level refactoring.