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 skills/pandysp/claude-plugins/silent-failuresnpx skills add pandysp/claude-plugins --skill silent-failuresgit clone --depth 1 https://github.com/pandysp/claude-pluginsWrote 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/pandysp/claude-plugins/silent-failures)<a href="https://agentmods.dev/skills/pandysp/claude-plugins/silent-failures"><img src="https://agentmods.dev/badge/skills/pandysp/claude-plugins/silent-failures.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.00091 | $0.01180 |
| Opus 5 | $0.00046 | $0.00590 |
| Sonnet 5 | $0.00018 | $0.00236 |
| Haiku 4.5 | $0.00009 | $0.00118 |
Grade A, and why
silent-failures 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 6d 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Silent failures: audit error handling for hidden failures
Apply the canonical hunter methodology in this skill through the strongest isolated review channel the host provides. The findings are for your grounding. Synthesize before surfacing anything to the user.
Hunter methodology
Audit error handling. The defects to hunt surface days after they happen, when the trail is cold: errors that occur without logging or user feedback, catch blocks that swallow what they did not expect, and fallbacks that hide the real problem.
Principles
- Silent failures are defects. An error without logging and user feedback is CRITICAL, however unlikely it looks.
- Error messages must be actionable. State what went wrong and what the user can do about it. Make the message specific enough to distinguish this error from its neighbors.
- Fallbacks must be explicit and justified. Falling back to alternative behavior without the user's awareness hides problems.
- Catch blocks must be specific. A broad catch suppresses errors nobody anticipated; enumerate what else it could swallow.
- Mocks belong in tests. Production code falling back to a mock or stub is an architectural problem, not error handling.
Process
- Locate every error-handling site in the diff or files under review: try/catch (or except, Result types), error callbacks and handlers, error-state branches, fallback logic and defaults-on-failure, log-and-continue sites, and optional chaining that can hide a failed operation.
- Scrutinize each site:
- Logging: right severity? Enough context (operation, IDs, state) to debug this six months from now?
- User feedback: does the user learn what went wrong and what to do next?
- Catch specificity: which unexpected error types could this catch accidentally suppress? List them.
- Fallback: requested or documented? Does it mask the underlying problem? Is it a mock outside tests?
- Propagation: should this bubble up instead? Does catching here prevent cleanup?
- Hunt the hiding patterns: empty catches, log-and-continue, default values returned on error without logging, retry loops that exhaust silently, and fallback chains with no explanation of why.
- Check project standards in the applicable host and repository instruction files: logging functions and severity conventions, error-ID systems for monitoring, and explicit rules on surfacing versus swallowing. Project standards override generic best practice.
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.
- 6d ago First seen · 103 lines · 91 tokens per session scan A 7efe5cc43d78
silent-failures is a skill published in the GitHub repository pandysp/claude-plugins (5 stars, last pushed 15d ago), licensed MIT. It adds 91 tokens to every session and 1,180 once invoked, about $0.0005 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 skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
azsdk-common-pipeline-analysis
Analyze Azure SDK CI/CD pipeline failures into a structured diagnosis, and define the required output format. Load this skill before calling azsdkanalyzepipeline, which returns raw failure data that this skill interprets and formats. USE FOR: "pipeline failed", "build failure", "CI check failing", "tests failing in…
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…