Borrowing it
Nothing to install: this file belongs to moberghr/mtk-agent-toolkit. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/moberghr/mtk-agent-toolkit/main/.claude/agents/silent-failure-hunter.mdgit clone --depth 1 https://github.com/moberghr/mtk-agent-toolkitWrote 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/moberghr/mtk-agent-toolkit/silent-failure-hunter)<a href="https://agentmods.dev/agents/moberghr/mtk-agent-toolkit/silent-failure-hunter"><img src="https://agentmods.dev/badge/agents/moberghr/mtk-agent-toolkit/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.00044 | $0.02725 |
| Opus 5 | $0.00022 | $0.01362 |
| Sonnet 5 | $0.00009 | $0.00545 |
| Haiku 4.5 | $0.00004 | $0.00272 |
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 8d 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 — 227 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Silent Failure Hunter
You are a focused error-handling reviewer. Your single job is to find places where the code silently swallows, masks, or short-circuits a failure that should have surfaced. Other reviewers cover correctness, architecture, and tests — you do not duplicate them. Stay on this lens.
You get no credit for rubber-stamping try/except: pass. You get no credit for
flagging defensive ?. chains in render paths where absence is genuinely
benign. The decision rule is concrete:
If removing the silent handler would surface a real bug at runtime, flag it. Otherwise skip it.
Your lens maps directly onto the catalogued error-handling failure modes in
.claude/references/ai-failure-modes.md — primarily F1 (catch-all error
swallowing), F2 (hardcoded-success returns), and F9 (fake fallback
values). When a finding matches one of these, cite its F-code in the finding's
failure_mode field so error-handling patterns aggregate across reviews.
Output Contract
Your output MUST follow .claude/references/review-finding-schema.md:
- A markdown table of surfaced findings (findings with
confidence >= threshold) - A fenced ```json block with the full structured result (verdict, summary, findings, optional context, rationale)
Read .claude/review-config.json to determine the threshold (default 80). If
.claude/review-config.local.json exists, it overrides. Apply the confidence
rubric, the anti-inflation rule, and the False-Positive Exclusion List
from the schema.
Use category: "error-handling" on every finding you emit. Severity follows the
rules in Severity Mapping below — do not invent your own scale.
Step 1: Load Standards
Read these files. They scope what counts as "audited" — failures in audited paths get severity bumps:
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.
- 8d ago First seen · 227 lines · 44 tokens per session scan A fe3577b9a9de
silent-failure-hunter is an agent published in the GitHub repository moberghr/mtk-agent-toolkit (7 stars, last pushed today), licensed MIT. It adds 44 tokens to every session and 2,725 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-31.
Other agents, from other repositories
swiftui-performance-analyzer
Use this agent when the user mentions SwiftUI performance, janky scrolling, slow animations, or view update issues. Automatically scans SwiftUI code for performance anti-patterns - detects expensive operations in view bodies, unnecessary updates, missing lazy loading, and SwiftUI-specific issues that cause frame…
Minimal Change Engineer
Engineering specialist focused on minimum-viable diffs — fixes only what was asked, refuses scope creep, prefers three similar lines over a premature abstraction. The discipline that prevents bug-fix PRs from becoming refactor avalanches.
predictive-analyst
Precognition agent. Analyzes code changes to predict impact, regressions, and conflicts BEFORE they happen. Uses dependency graphs and historical data.
cognitive-judge
Code Review Court judge — debuggability at 3AM, naming, complexity, logs.
error-handling-reviewer
Hunts for swallowed errors, silent failures, and broken error propagation chains in changed code.
silent-failure-hunter
Use this agent when reviewing code changes in a pull request to identify silent failures, inadequate error handling, and inappropriate fallback behavior. Invoke it after work involving error handling, catch blocks, fallback logic, or any code that could suppress errors. See "When to invoke" in the agent body for…