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/Fmarzochi/EGCWrote 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/fmarzochi/egc/silent-failure-hunter)<a href="https://agentmods.dev/agents/fmarzochi/egc/silent-failure-hunter"><img src="https://agentmods.dev/badge/agents/fmarzochi/egc/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.00024 | $0.00243 |
| Opus 5 | $0.00012 | $0.00121 |
| Sonnet 5 | $0.00005 | $0.00049 |
| Haiku 4.5 | $0.00002 | $0.00024 |
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
3 near-identical copies found in the catalogue:
- silent-failure-hunter — 88% identical, 3 lines differ
- silent-failure-hunter — 88% identical, 3 lines differ
- silent-failure-hunter — 88% identical, 3 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 · 52 lines · 24 tokens per session scan A 1c01df907533
silent-failure-hunter is an agent published in the GitHub repository Fmarzochi/EGC (49 stars, last pushed yesterday), licensed Apache-2.0. It adds 24 tokens to every session and 243 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-09-03.
Other agents, from other repositories
jd-fix-agent
You are a judgment-day surgical fix agent. Execute the fix instructions provided in the delegate prompt exactly.
bug-hunter
Use this agent when reviewing local code changes or in the pull request to identify bugs and critical issues through systematic root cause analysis. This agent should be invoked proactively after completing a logical chunk of work.
fec-performance-optimizer
Front-end performance analysis and optimization specialization: Core Web Vitals, packaging volume, runtime and rendering, network and cache, memory leak troubleshooting; can cooperate with Lighthouse, Bundle analysis and Profiler. Use it when users mention page slowness, lag, first screen, package size, poor…
fec-ui-checker
Use this subagent to troubleshoot visual defects, layout confusion, CSS issues, responsive exceptions, and inconsistencies between interaction and design in the front-end UI, and save the report as a Markdown file. Supports obtaining design data from Figma, Sketch, MasterGo, Pixso, Moko, and Mock, compares the design…
code-reviewer-bug
name: code-reviewer-bug description: Specialized code reviewer for bug patterns — null safety, race conditions, resource leaks, logic and error-handling defects. Returns scored findings (severity × impact × confidence). skills: code-review model: inherit.
oracle
Highest-reasoning tier, read-only. Use for (a) REVIEW of critical diffs — security, auth, payments, data migrations, public API contracts; (b) SOLVE — designing novel algorithms or root-causing bugs that survived two fix attempts. Expensive — invoke deliberately, with a complete dossier.