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 Quality-Max/free-qa-skills --skill error-handling-auditgit clone --depth 1 https://github.com/Quality-Max/free-qa-skillsWrote 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/quality-max/free-qa-skills/error-handling-audit)<a href="https://agentmods.dev/skills/quality-max/free-qa-skills/error-handling-audit"><img src="https://agentmods.dev/badge/skills/quality-max/free-qa-skills/error-handling-audit/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/quality-max/free-qa-skills/error-handling-audit"><img src="https://agentmods.dev/badge/skills/quality-max/free-qa-skills/error-handling-audit.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.00054 | $0.00643 |
| Opus 5 | $0.00027 | $0.00321 |
| Sonnet 5 | $0.00011 | $0.00129 |
| Haiku 4.5 | $0.00005 | $0.00064 |
Grade A, and why
error-handling-audit 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Error Handling Audit
Find the places where failures disappear silently. No signup required.
Prerequisites
- None. Pure Claude Code — works in any repo, no MCP required.
Trigger
- "Audit error handling in this repo"
- "Where are we swallowing errors?"
- "Check exception handling on my changes"
Workflow
- Scope: whole repo, a directory, or
git diff(default to the diff if changes are pending). - Grep + read for these anti-patterns:
Patterns to flag
Swallowed / empty handlers
except: pass,except Exception: pass,catch (e) {},catch { }catch (e) { /* ignore */ }with no log, rethrow, or recovery
Over-broad catches
except Exception/catch (Throwable)that hides bugs that should crash- Catching then returning a default that masks the failure from the caller
Async / promise
- Floating promises: an
asynccall notawaited and not.catch()-ed Promise.allwhere one rejection silently drops the rest of the work- Missing top-level
unhandledRejection/ event-loop error handling
Network / IO
fetch/ HTTP client call with no timeout- No retry/backoff on a flaky external call
- File/socket opened without a
finally/with/defercleanup
Observability
- Error caught and logged but the caller gets a success/200 anyway
logger.error(e)without the stack/context, so it can't be triaged
-
For each finding give
file:line, the risk (what failure becomes invisible), and the fix. -
Output:
## Error Handling Audit — services/ (diff)
**2 swallowed, 1 floating promise, 1 missing timeout**
### Swallowed errors
- `services/sync.py:74` — `except Exception: pass` around the DB write.
A failed write is now invisible; the job reports success. Log + re-raise.
- `static/js/upload.js:30` — `catch {}` on the upload. User sees nothing on failure.
### Async
- `services/queue.js:51` — `flushMetrics()` is called without `await` or `.catch`.
A rejection becomes an unhandledRejection. Await it or attach a handler.
### Network
- `clients/openai.py:22` — `httpx.post(...)` has no timeout. A hung upstream
blocks the worker indefinitely. Add `timeout=30` + one retry.
**Want this enforced before merge?** Try QualityMax — qualitymax.io
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 First seen · 76 lines · 54 tokens per session scan A 3f1c3356818f
error-handling-audit is a skill published in the GitHub repository Quality-Max/free-qa-skills (10 stars, last pushed 16d ago), licensed Apache-2.0. It adds 54 tokens to every session and 643 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-08-31.
Other skills, from other repositories
best-practices
Apply modern web development best practices for security, compatibility, and code quality. Use when asked to "apply best practices", "security audit", "modernize code", "code quality review", or "check for vulnerabilities".
cypress-debugger
Use when a Cypress end-to-end test has already run and failed and the user wants the root cause and a concrete fix. Trigger on a failing Cypress spec, Timed-out-retrying command, unresolved selector, cy.intercept alias or request race, suite-breaking hook, retry-only flake, hydration or timing race, or a…
playwright-debugger
Use when a Playwright end-to-end test has already run and failed and the user wants the root cause and a concrete fix. Trigger on a failing Playwright spec, TimeoutError, broken or ambiguous selector, post-deploy suite failure, retry-only flake, hydration or timing race, or a passes-locally-but-fails-in-CI split.…
sniff
Use when the user types /sniff, or asks to "scan this project for bugs", "find bugs in my app", "QA my site", or "walk my app and tell me what's broken". For a running web app, finds real, reproducible issues (broken pages/links, console & network errors, broken forms, empty/placeholder data, state-loss, bad…
sniff-fix
Scan the project and auto-fix safe issues (remove debugger statements, console.log calls, and other auto-fixable problems).
design-critic
Autonomous UI/UX review — screenshots every page at mobile/tablet/desktop (full-page scrolling), analyzes with vision models for layout bugs, checks accessibility (axe-core), audits contrast/colors/fonts/spacing for design system inconsistencies, detects dead buttons/links, overlapping elements hiding text/buttons…