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/talayash/agentrium/silent-failure-huntergit clone --depth 1 https://github.com/talayash/agentriumWrote 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/talayash/agentrium/silent-failure-hunter)<a href="https://agentmods.dev/agents/talayash/agentrium/silent-failure-hunter"><img src="https://agentmods.dev/badge/agents/talayash/agentrium/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 | $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 4d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- silent-failure-hunter — 100% identical, 0 lines differ
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.
- 4d ago First seen · 51 lines · 24 tokens per session scan A 004ce0389356
silent-failure-hunter is an agent published in the GitHub repository talayash/agentrium (39 stars, last pushed 3d 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
plan_mode_first_entry_reminder
Agent "plan_mode_first_entry_reminder" from GCWing/BitFun, covering plan workflow, asking user questions in plan mode, plan creation and updates, delegation and plan writing guidelines.
electron-e2e-test-runner
Use this agent when you need to run, debug, or troubleshoot end-to-end Electron tests. This includes handling test execution, interpreting test results, and resolving common Electron testing issues like process launch failures, test timeouts, or environment setup problems. Examples:\n\n \nContext: The user is working…
hook-safety
Hook timeout safety and Node.js ESM conventions reviewer. Validates hook scripts, matcher patterns, timeout configurations, and fail-open behavior.
user-perspective-critic
Top-down критика глазами реального пользователя продукта. Читает PRODUCT.md и domain-rules.yaml, спрашивает "какой сценарий не покрыт?", "оптимизируем по правильной метрике?", "работает ли при голосовом вводе по-русски?". Запускается параллельно с test-researcher в /feature heavy path.
architect
Системный архитектор. Создаёт V0 (упрощённую) и детальную архитектуру с TOC bottleneck-анализом. Применяет Карпати Simplicity First (≤10 компонентов). Готовит docs/ARCHITECTURE.md.
browser-tester
Браузерные e2e-тесты через Playwright (запуск из Bash) — основной путь. Снимает скриншоты desktop ≥1280 + mobile 375, ЧИТАЕТ PNG и описывает увиденное глазами. Layer 3 в three-layer verification, запускается из /verify для UI-фичей.