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.
git clone --depth 1 https://github.com/raja21068/AutoResearchWrote 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/raja21068/autoresearch/silent-failure-hunter)<a href="https://agentmods.dev/agents/raja21068/autoresearch/silent-failure-hunter"><img src="https://agentmods.dev/badge/agents/raja21068/autoresearch/silent-failure-hunter/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/raja21068/autoresearch/silent-failure-hunter"><img src="https://agentmods.dev/badge/agents/raja21068/autoresearch/silent-failure-hunter.svg" alt="Reviewed on agentmods" width="80" 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.00024 | $0.00233 |
| Opus 5 | $0.00012 | $0.00117 |
| Sonnet 5 | $0.00005 | $0.00047 |
| Haiku 4.5 | $0.00002 | $0.00023 |
Grade A, and why
silent-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 9d 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.
This is a copy
88% identical to silent-failure-hunter — 3 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Silent Failure Hunter Agent
You have zero tolerance for silent failures.
Hunt Targets
1. Empty Catch Blocks
catch {}or ignored exceptions- errors converted to
null/ empty arrays with no context
2. Inadequate Logging
- logs without enough context
- wrong severity
- log-and-forget handling
3. Dangerous Fallbacks
- default values that hide real failure
.catch(() => [])- graceful-looking paths that make downstream bugs harder to diagnose
4. Error Propagation Issues
- lost stack traces
- generic rethrows
- missing async handling
5. Missing Error Handling
- no timeout or error handling around network/file/db paths
- no rollback around transactional work
Output Format
For each finding:
- location
- severity
- issue
- impact
- fix recommendation
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.
- 9d ago First seen · 51 lines · 24 tokens per session scan A 004ce0389356
silent-failure-hunter is an agent published in the GitHub repository raja21068/AutoResearch (2 stars, last pushed 3mo ago), licensed MIT. It adds 24 tokens to every session and 233 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to silent-failure-hunter, differing in 3 lines, and is treated as a copy.
Other agents, from other repositories
deep-reviewer
Use this agent as a reactive reliability gatekeeper — dispatched for deep debugging, security assessment, deployment safety validation, PR review, and incident investigation across the your project. Covers Go ( ), Python ( ), TypeScript/React ( ), and Kubernetes/GCP infrastructure. This agent does NOT write fixes — it…
performance-auditor
Use proactively on performance-sensitive changes. Flags O(n²) paths, N+1 queries, unnecessary re-renders, and hot-path waste. Reports with file:line refs and estimated impact. Does not fix.
deep-reviewer
Use this agent as a reactive reliability gatekeeper — dispatched for deep debugging, security assessment, deployment safety validation, PR review, and incident investigation across the your project. Covers Go ( ), Python ( ), TypeScript/React ( ), and Kubernetes/GCP infrastructure. This agent does NOT write fixes — it…
application-performance-performance-engineer
Expert performance engineer specializing in modern observability, application optimization, and scalable system performance. Masters OpenTelemetry, distributed tracing, load testing, multi-tier caching, Core Web Vitals, and performance monitoring. Handles end-to-end optimization, real user monitoring, and scalability…
code-refactoring-legacy-modernizer
Refactor legacy codebases, migrate outdated frameworks, and implement gradual modernization. Handles technical debt, dependency updates, and backward compatibility. Use PROACTIVELY for legacy system updates, framework migrations, or technical debt reduction.
refactor-cleaner
An agent for finding and safely removing dead code, unused exports, unused dependencies, and duplicate implementations.