silent-failure-hunter

silent-failure-hunter is an agent for Claude Code from RaNDoM6913/claude-code-superkit. It costs 64 tokens per session (2,867 once invoked), scanned A, original, MIT.

A code reviewer that looks for errors being hidden or ignored, such as empty catch blocks, discarded promises, and fallbacks that conceal failures.

In plain words
What is it for?
It scans several programming languages for swallowed errors and reports where logging, metrics, alerts, or clearer handling may be missing.
Why use it?
It helps prevent software from appearing to work while quietly losing errors that developers need to see.

Agent for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: model in frontmatter; mentions CLAUDE.md; mentions AGENTS.md.

Good fit It scans several programming languages for swallowed errors and reports where logging, metrics, alerts, or clearer handling may be missing.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/random6913/claude-code-superkit/silent-failure-hunter
Install

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.

Clone the repo
git clone --depth 1 https://github.com/RaNDoM6913/claude-code-superkit

Made for: Claude Code.

Wrote 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.

agentmods badge for silent-failure-hunter

README.md
[![agentmods](https://agentmods.dev/badge/agents/random6913/claude-code-superkit/silent-failure-hunter/github.svg)](https://agentmods.dev/agents/random6913/claude-code-superkit/silent-failure-hunter)
Your own site
<a href="https://agentmods.dev/agents/random6913/claude-code-superkit/silent-failure-hunter"><img src="https://agentmods.dev/badge/agents/random6913/claude-code-superkit/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.

agentmods 80×15 button for silent-failure-hunter

Your own site · 80×15
<a href="https://agentmods.dev/agents/random6913/claude-code-superkit/silent-failure-hunter"><img src="https://agentmods.dev/badge/agents/random6913/claude-code-superkit/silent-failure-hunter.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 64 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,867 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00064 $0.02867
Opus 5.5 $0.00026 $0.01147
Sonnet 5.5 $0.00013 $0.00573
Haiku 4.5 $0.00006 $0.00287

Measured 1mo ago against content hash 86ece7acf501, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 1mo 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.

packages/core/agents/silent-failure-hunter.md · 277 lines

How it starts

The opening of the file, as written. The whole thing — 277 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Silent Failure Hunter

Reviewer agent that finds code eating errors silently: empty catch blocks, except: pass, .catch(() => []), log-and-forget, fallback-to-empty. Dispatched by the /review pipeline for changed files, by the /dev Critic phase, after new error-prone surface (network, file, parse, auth), and for post-incident or periodic sweeps.

Hard Rules

  1. Treat every error suppression as a finding until BOTH a disclosure comment AND a parallel observability mechanism (log, metric, or alert) are present.
  2. Cite only file:line you actually Read this session. If a referenced file cannot be found, output NOT FOUND: <path> — never invent content.
  3. Severity is exactly CRITICAL / WARNING / SUGGESTION; Confidence is exactly HIGH / MEDIUM / LOW. Route LOW-confidence items to Open Questions — never drop them.
  4. Discovery surfaces every candidate; only triage filters. Do not pre-filter during discovery.
  5. A clean review (0 findings) is a valid result — do not manufacture findings.
  6. Emit the Output Contract exactly: findings, summary with per-category counts, Open Questions.

Phase 0 — Load Project Context

Read if present, skip silently if absent: CLAUDE.md or AGENTS.md (project error-handling pattern — panics, Result, exceptions, custom error type); docs/architecture/backend-layers.md; observability config (Sentry / Datadog / structured logger); any error-policy doc. Use it to: distinguish legitimate expected-fail-and-recover patterns from accidental silencers. Violations of DOCUMENTED conventions → report with HIGH confidence instead of MEDIUM.

Process

1. Discover. Determine scope (changed files when invoked from a review; otherwise the requested paths). Run every seed grep below over the scope and record each hit as a candidate. Done when: all seeds ran over the full scope.

Seed greps (pass 1 — deliberately broad; alternation-free, ripgrep-safe):

  • Category A: catch, except, ^\s*_ =, _, err, let _ =, unwrap_or_default, \|\| true, 2>/dev/null
  • Category B: \.catch\(, create_task, tokio::spawn
  • Category F: @ts-ignore, type: ignore, nolint, eslint-disable
  • Categories C/D/E have no reliable seed — they surface while reading the context of A/B hits in pass 2.

Read the full file on GitHub · 277 lines

Changes

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.

  1. 1mo ago First seen · 277 lines · 64 tokens per session scan A 86ece7acf501

Subscribe to this mod's changes

silent-failure-hunter is an agent published in the GitHub repository RaNDoM6913/claude-code-superkit (3 stars, last pushed 9d ago), licensed MIT. It adds 64 tokens to every session and 2,867 once invoked, about $0.0003 per session on Opus 5.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.

Related

Other agents, from other repositories

Hypatia

Critic and devil's advocate instrument. Challenges strategy before commitment — finds the strongest counterargument, names what the AIgent missed, probes for hidden assumptions. Use before any significant decision. Read-only — she critiques, never builds. Voice is skeptical but constructive.

wrg32786/aigent-os · 55 tokens

debugger

Turns a failure, stack trace, or bug report into ranked hypotheses and the cheapest test to confirm each. Use when something is broken and the cause is not yet known.

emtcmca/promptsmith · 37 tokens

swift-build-resolver

Swift/Xcode build, compilation, and dependency error resolution specialist. Fixes swift build errors, Xcode build failures, SPM dependency issues, and code signing problems with minimal changes. Use when Swift builds fail.

affaan-m/ECC · 48 tokens

deep-research-fetcher

Fetches one disjoint batch of URLs into a nav-deep-research run as fenced source notes. Spawned in parallel waves by the nav-deep-research skill (step 2 sweep, step 4 gap-fetch). Never searches for new URLs on its own, never reads other fetchers' batches.

qf-studio/navigator · 69 tokens

doctrine-performance-optimizer

Read-only performance audit of Doctrine usage: N+1 queries, fetch modes, batch processing, missing indexes, and caching opportunities. Use proactively after adding entities, relations, repository queries, or when a page/endpoint is reported slow.

dev-toolings/superpowers-symfony · 53 tokens

mb-debugger

Systematic-debugging specialist for memory-bank. Use when a bug, failing test, flaky test, crash, regression, or unexpected behaviour must be explained and fixed — finds the root cause with evidence before any fix, then lands a failing test, a single fix, and verification output.

fockus/skill-memory-bank · 61 tokens