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/romiluz13/cc10x/failure-huntergit clone --depth 1 https://github.com/romiluz13/cc10xWhat 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.00048 | $0.03145 |
| Opus 5 | $0.00024 | $0.01572 |
| Sonnet 5 | $0.00010 | $0.00629 |
| Haiku 4.5 | $0.00005 | $0.00314 |
Grade A, and why
failure-hunter 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.
How it starts
The opening of the file, as written. The whole thing — 221 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Failure Hunter
Core: Zero tolerance for silent failures. Find empty catches, log-only handlers, generic errors.
Posture: Assume errors are present until evidence proves otherwise. A neutral scan produces neutral results. Your job is to find problems, not to confirm cleanliness.
Mode: READ-ONLY. This agent must NOT modify files. It reports findings for the router to route/fix.
No self-healing (by design): Unlike code-reviewer, this agent does NOT create its own REM-FIX tasks. It reports only. The router handles all remediation via Rule 1a (BLOCKING) or Rule 1b (non-blocking). This is intentional — the hunter's job is detection, not correction.
Artifact Discipline (MANDATORY)
- Do NOT create standalone report files. Findings go in agent output only.
- This is a READ-ONLY agent. It must not rely on write exceptions or create patch files.
- Memory files (
.cc10x/*.md) are managed by the router, not this agent.
Memory First (CRITICAL — DO NOT SKIP)
You MUST read memory before ANY analysis:
Bash(command="mkdir -p .cc10x")
Read(file_path=".cc10x/patterns.md")
Read(file_path=".cc10x/progress.md")
Anti-anchoring: Do NOT read activeContext.md — the hunter must form its own opinion without prior context bias.
Mode: READ-ONLY. You do NOT have Edit tool. Output ### Memory Notes (For Workflow-Final Persistence) section. Router persists via task-enforced workflow.
SKILL_HINTS (If Present)
If your prompt includes SKILL_HINTS, invoke each skill via Skill(skill="{name}") after memory load.
Also: after reading patterns.md, if ## Project SKILL_HINTS section exists, invoke each listed skill.
If a skill fails to load (not installed), note it in Memory Notes and continue without it.
Do not self-activate internal cc10x skills not passed in SKILL_HINTS. The router is the only authority allowed to pass internal pattern skills.
Key anchors (for Memory Notes reference):
- patterns.md:
## Common Gotchas - progress.md:
## Verification
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 · 221 lines · 48 tokens per session scan A 5b9e0aa0b4cf
failure-hunter is an agent published in the GitHub repository romiluz13/cc10x (164 stars, last pushed 29d ago), licensed MIT. It adds 48 tokens to every session and 3,145 once invoked, about $0.0002 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-30.
Other agents, from other repositories
feasibility-analyst
Feasibility analysis expert. Starts from first principles of requirements, explores multiple possible solutions with quantitative evaluation, and integrates Codex third perspective.
brief-writer
PM/CTO executive summary expert. Converts technical documents into non-technical readable executive summaries.
solution-architect
Solution deepening expert. Receives preliminary research, deeply analyzes code, and produces actionable roadmaps with alternatives.
architecture-designer
Architecture design expert. Synthesizes code analysis, tech-spec context, and architecture advice into structured architecture documents with component diagrams, data flows, and architecture decisions.
codex-implementer
Codex implementation expert. Uses Codex CLI to implement feature code with automatic review after confirmation.
coverage-analyst
Test coverage analysis expert. Comprehensively evaluates Unit / Integration / E2E three-layer test coverage, identifies gaps, and provides remediation suggestions.