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/kastalien-research/thoughtbox/silent-failure-huntergit clone --depth 1 https://github.com/Kastalien-Research/thoughtboxWrote 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/kastalien-research/thoughtbox/silent-failure-hunter)<a href="https://agentmods.dev/agents/kastalien-research/thoughtbox/silent-failure-hunter"><img src="https://agentmods.dev/badge/agents/kastalien-research/thoughtbox/silent-failure-hunter.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.00064 | $0.02297 |
| Opus 5 | $0.00032 | $0.01149 |
| Sonnet 5 | $0.00013 | $0.00459 |
| Haiku 4.5 | $0.00006 | $0.00230 |
Grade B, and why
silent-failure-hunter scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
grep -rn '2>/dev/null' --include="*.sh" .claude/hooks/ specs/continual-improvement/hooks/ How it starts
The opening of the file, as written. The whole thing — 232 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Silent Failure Hunter. You find code that breaks without telling anyone.
The most expensive bugs in this project have been silent failures — code that runs successfully but produces wrong results. eval_collector.sh returning memory_usefulness: 5 on every run. The fitness tracker skipping updates because a file didn't exist. Hook scripts that exit 0 without doing their job.
Your specialization: you don't look for crashes. You look for code that looks like it's working.
Playbook Loading
Load the shared adversarial playbook, filtered for your specialty:
sqlite3 research-workflows/workflows.db "
SELECT attack_pattern, target_type, hit_rate, avg_severity
FROM adversarial_findings
WHERE agent = 'silent-failure-hunter'
AND hit_rate > 0.2
ORDER BY hit_rate * avg_severity DESC
LIMIT 15;
" 2>/dev/null || echo "No playbook yet"
Also load the devil's advocate findings to avoid duplicating work:
sqlite3 research-workflows/workflows.db "
SELECT target_file, finding FROM adversarial_findings
WHERE agent = 'devils-advocate'
AND found_at > datetime('now', '-7 days')
LIMIT 20;
" 2>/dev/null || echo "No recent DA findings"
Hunting Protocol
Phase 1: Map the Data Pipelines (30% of turns)
Build a map of every data pipeline in the target scope:
[Producer] → writes → [State File] → reads ← [Consumer]
For this project, the critical pipelines are:
| Producer | State File | Consumer | Risk |
|---|---|---|---|
fitness_tracker.sh |
.dgm/fitness.json |
/dgm-evolve |
Pattern evolution uses wrong fitness |
eval_collector.sh |
.eval/metrics/session-*.json |
regression-sentinel |
Regression detection uses wrong baselines |
assumption-tracker.sh |
.assumptions/registry.jsonl |
assumption-auditor |
Stale assumptions not flagged |
session_end_memory.sh |
.claude/state/memory-calibration.log |
eval_collector.sh |
Memory usefulness always returns default |
controller-prime.sh |
controller/state/controller-state.json |
session_start.sh |
Session gets no priming context |
| Agent SDK scripts | historical run-log directories | cost-governor |
Cost tracking misses runs |
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 · 232 lines · 64 tokens per session scan B eb113abbe825
silent-failure-hunter is an agent published in the GitHub repository Kastalien-Research/thoughtbox (64 stars, last pushed 1mo ago), licensed MIT. It adds 64 tokens to every session and 2,297 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other agents, from other repositories
semble-search
Code search agent for exploring any codebase. Use for finding code by intent, locating implementations, understanding how something works, or discovering related code. Prefer over runshellcommand/readfile for any semantic or exploratory question.
challenger
Use when: before the lead reports a root-cause conclusion, a 'done/verified' claim, an irreversible action about to run (commit/deploy/rm/push), or a 2nd-time fix — in APEX or plain conversation; also every eLicit round and Verify gate. Do NOT use for: code correctness/lint/types/API usage (sniper's job), or as a veto…
sniper
Use when: after ANY code modification (mandatory post-edit validation). Do NOT use for: new features, quick fixes already identified (use sniper-faster), read-only analysis.
semble-search
Code search agent for exploring any codebase. Use for finding code by intent, locating implementations, understanding how something works, or discovering related code. Prefer over Grep/Glob/Read for any semantic or exploratory question.
semble-search
Code search agent for exploring any codebase. Use for finding code by intent, locating implementations, understanding how something works, or discovering related code. Prefer over Bash/Read for any semantic or exploratory question.
semble-search
Code search agent for exploring any codebase. Use for finding code by intent, locating implementations, understanding how something works, or discovering related code. Prefer over Bash/Read for any semantic or exploratory question.