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 skills add RaNDoM6913/claude-code-superkit --skill 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/skills/random6913/claude-code-superkit/silent-failure-hunter)<a href="https://agentmods.dev/skills/random6913/claude-code-superkit/silent-failure-hunter"><img src="https://agentmods.dev/badge/skills/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.
<a href="https://agentmods.dev/skills/random6913/claude-code-superkit/silent-failure-hunter"><img src="https://agentmods.dev/badge/skills/random6913/claude-code-superkit/silent-failure-hunter.svg" alt="Reviewed on agentmods" width="80" 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.00037 | $0.02812 |
| Opus 5.5 | $0.00015 | $0.01125 |
| Sonnet 5.5 | $0.00007 | $0.00562 |
| Haiku 4.5 | $0.00004 | $0.00281 |
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 10d 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 — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Silent Failure Hunter
Trace failures from the operation through its handler, recovery, caller, and operational signals. Find cases where required failure information or recovery is lost. Silence is a clue, not a verdict: an intentional best-effort operation or expected miss may need neither an exception nor a log per occurrence.
Scope, context, and authority
Read applicable AGENTS.md first, then relevant error policy, architecture, and observability configuration. Establish the selected diff/base or explicit audit scope; do not sweep the whole repository unless requested. Inspect actual code, surrounding control flow, and relevant callers/consumers. Confirm runtime/library versions before relying on version-specific exception, task, or shell behavior.
Review only. Propose fixes, but do not edit code, change logging/alerts, enqueue retries, trigger production failures, or perform external writes without a distinct authorized action. Tests or command examples are not permission to contact real services. Use safe, authorized local checks when needed and redact secrets/private data from logs, excerpts, and reports.
Honor explicit task/project model and effort routing and acceptance ownership. Disclose INDEPENDENT versus INLINE SELF-REVIEW. Report requested/configured route separately from observed runtime values with evidence or UNVERIFIED; missing runtime identity alone creates no new gate. Mandatory independent/Astra acceptance remains pending when unavailable.
Discover, trace, then triage
Use patterns below to locate candidates. Before reporting, establish:
- Which operation can fail, under which concrete input/state, and which errors are expected versus unexpected.
- Whether the failure reaches an owner through a return value, exception/cause, result, task handle, status, event, or metric. Read the relevant caller and state transition; a local handler is not the entire error contract.
- Whether recovery actually restores the promised result, explicitly returns degraded/partial success, or falsely reports success. Logging alone does not correct a wrong state transition; propagation alone may be sufficient if an upstream boundary owns diagnostics.
- Whether the chosen signal is adequate for the consequence without leaking data or flooding logs. Do not demand a comment plus metric plus alert on every ignored error.
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.
- 10d ago Changed · -102 lines · -6 tokens per session 4995cdaec331
- 1mo ago First seen · 279 lines · 43 tokens per session scan A 8130aacff8a3
silent-failure-hunter is a skill published in the GitHub repository RaNDoM6913/claude-code-superkit (3 stars, last pushed 10d ago), licensed MIT. It adds 37 tokens to every session and 2,812 once invoked, about $0.0001 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.
Other skills, from other repositories
Diagnose
When something feels off, type /diagnose and describe the symptom. The skill walks the seven-layer stack (kernel, skills, hooks, daemons, vault, doctrine, principal config) and reports which layer is most likely responsible. Caddy pattern applied to debugging.
First 10 Moves
The exact operational recon sequence for an unfamiliar codebase or unfamiliar area. Replaces "ask the human to clarify" with "read the code first." Most clarification questions are answered by 5 minutes in the relevant file - this skill enforces reading before asking.
Stuck
Walk the 6-rung escalation ladder before declaring stuck or asking the principal. Most "stuck" is actually "haven't tried the next approach." Stopping is the last resort, not the first response.
learn-from-failure
When a failure occurs, classify it, check for repetition, and produce a durable artifact that prevents recurrence.
solution-hunt
When blocked, systematically search for legitimate alternate routes before declaring inability.
system-check
Read-only installation smoke test for skills, daemons, operational memory, cognitive runtime, nightly freshness, terminal evidence, and unique route ownership.