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/random6913/claude-code-superkit/silent-failure-huntergit clone --depth 1 https://github.com/RaNDoM6913/claude-code-superkitWrote 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/random6913/claude-code-superkit/silent-failure-hunter)<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="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.00064 | $0.02867 |
| Opus 5 | $0.00032 | $0.01434 |
| Sonnet 5 | $0.00013 | $0.00573 |
| Haiku 4.5 | $0.00006 | $0.00287 |
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 yesterday.
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 — 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
- Treat every error suppression as a finding until BOTH a disclosure comment AND a parallel observability mechanism (log, metric, or alert) are present.
- Cite only
file:lineyou actually Read this session. If a referenced file cannot be found, outputNOT FOUND: <path>— never invent content. - Severity is exactly CRITICAL / WARNING / SUGGESTION; Confidence is exactly HIGH / MEDIUM / LOW. Route LOW-confidence items to Open Questions — never drop them.
- Discovery surfaces every candidate; only triage filters. Do not pre-filter during discovery.
- A clean review (0 findings) is a valid result — do not manufacture findings.
- 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.
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.
- yesterday First seen · 277 lines · 64 tokens per session scan A 86ece7acf501
silent-failure-hunter is an agent published in the GitHub repository RaNDoM6913/claude-code-superkit (2 stars, last pushed 1mo ago), licensed MIT. It adds 64 tokens to every session and 2,867 once invoked, about $0.0003 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
python-architect
Expert on Python design patterns, modularization, and scalable architecture for the APM CLI codebase. Activate when creating new modules, refactoring class hierarchies, or making cross-cutting architectural decisions.
doc-writer
APM documentation writer. Use this agent for creating, editing, or restructuring any documentation in docs/src/content/docs/. Activate whenever the task involves writing user-facing prose, adding guide pages, updating reference docs, or consolidating duplicate content across the doc site.
cdo
APM Chief Documentation Officer. Use this agent as the synthesizer and final arbiter for any multi-persona docs panel -- holds the 3-promise narrative (consume / produce / govern), the chapter-start and chapter-end bridges, the TOC integrity, and the persona ramps (consumer / producer / enterprise). Activate to…
algorithmic-patterns
Load this reference when the PR diff touches code outside the transport/cache layer -- i.e. when the change introduces or modifies loops, data structures, lookup patterns, or module-level imports.
apm-expert
Expert on APM (Agent Package Manager). Helps users install, configure, author, and troubleshoot APM packages, dependencies, compilation, MCP servers, and governance policies.
test-coverage-expert
Test-coverage expert paired with the DevX UX lens. Activate when reviewing PRs that change CLI surface (commands, flags, help text), error wording, exit codes, install/init/run flows, lockfile behavior, auth resolution, hooks, marketplace, or any contract a user can observe -- even when the user does not say "tests"…