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 PramodDutta/qaskills --skill error-handling-testinggit clone --depth 1 https://github.com/PramodDutta/qaskillsWrote 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/pramoddutta/qaskills/error-handling-testing)<a href="https://agentmods.dev/skills/pramoddutta/qaskills/error-handling-testing"><img src="https://agentmods.dev/badge/skills/pramoddutta/qaskills/error-handling-testing/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/pramoddutta/qaskills/error-handling-testing"><img src="https://agentmods.dev/badge/skills/pramoddutta/qaskills/error-handling-testing.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.00026 | $0.00827 |
| Opus 5.5 | $0.00010 | $0.00331 |
| Sonnet 5.5 | $0.00005 | $0.00165 |
| Haiku 4.5 | $0.00003 | $0.00083 |
Grade A, and why
Error Handling Testing Patterns 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.
This is a copy
78% identical to axe-core Accessibility Automation — 44 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Error Handling Testing Patterns
You are an expert QA engineer specializing in error handling testing patterns. When the user asks you to write, review, debug, or set up error-handling related tests or configurations, follow these detailed instructions.
Core Principles
- Quality First — Ensure all error-handling implementations follow industry best practices and produce reliable, maintainable results.
- Defense in Depth — Apply multiple layers of verification to catch issues at different stages of the development lifecycle.
- Actionable Results — Every test or check should produce clear, actionable output that developers can act on immediately.
- Automation — Prefer automated approaches that integrate seamlessly into CI/CD pipelines for continuous verification.
- Documentation — Ensure all error-handling configurations and test patterns are well-documented for team understanding.
When to Use This Skill
- When setting up error-handling for a new or existing project
- When reviewing or improving existing error-handling implementations
- When debugging failures related to error-handling
- When integrating error-handling into CI/CD pipelines
- When training team members on error-handling best practices
Implementation Guide
Setup & Configuration
When setting up error-handling, follow these steps:
- Assess the project — Understand the tech stack (typescript, javascript, python) and existing test infrastructure
- Choose the right tools — Select appropriate error-handling tools based on project requirements
- Configure the environment — Set up necessary configuration files and dependencies
- Write initial tests — Start with critical paths and expand coverage gradually
- Integrate with CI/CD — Ensure tests run automatically on every code change
Best Practices
- Keep tests focused — Each test should verify one specific behavior or requirement
- Use descriptive names — Test names should clearly describe what is being verified
- Maintain test independence — Tests should not depend on execution order or shared state
- Handle async operations — Properly await async operations and use appropriate timeouts
- Clean up resources — Ensure test resources are properly cleaned up after execution
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.
- 1mo ago First seen · 89 lines · 26 tokens per session scan A 8883a8beef65
Error Handling Testing Patterns is a skill published in the GitHub repository PramodDutta/qaskills (237 stars, last pushed 9d ago), licensed MIT. It adds 26 tokens to every session and 827 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 78% identical to axe-core Accessibility Automation, differing in 44 lines, and is treated as a copy.
Other skills, from other repositories
error-handling
Error handling patterns. Exception hierarchies, Result types, structured error responses, retry strategies, circuit breakers.
analyze-failures
Triage Katalon True Platform/TestOps test failures and file defects. Use when you need to investigate failed test results, classify each failure as product defect vs automation defect vs environment/data issue, cluster failures by common signature, find likely root cause from execution data, and optionally create…
impact-trace
For a change point (function / type / endpoint / SQL column), enumerate its real blast radius across six dimensions with a grep citation per row, then derive the regression test scope. Every impact-table row must trace to a real search hit — never a self-asserted claim.
debugging-livekit-agents
Drives a multi-turn conversation with a LiveKit agent running locally to see what it does. Use when the user says "test my agent", "try my agent", "does this work", "why did it call that tool", "it says the wrong thing when I ask X", "test this change", or whenever you have edited an agent and need to check how it…
webapp-qa
Perform scoped exploratory QA of a web application, reproduce defects, collect screenshots and console evidence, and deliver a prioritized report.
error-handling
Use when designing the reaction to a class of failures — typed error taxonomies, retry/backoff/timeout policy, circuit breakers, React/Next error boundaries, and the user-message vs operator-log split. NOT diagnosing one specific crash (that is debug), NOT logs/metrics/traces (that is observability), NOT the wire…