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/srstomp/pokayokay/error-handlingnpx skills add srstomp/pokayokay --skill error-handlinggit clone --depth 1 https://github.com/srstomp/pokayokayWrote 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/srstomp/pokayokay/error-handling)<a href="https://agentmods.dev/skills/srstomp/pokayokay/error-handling"><img src="https://agentmods.dev/badge/skills/srstomp/pokayokay/error-handling.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.00043 | $0.00692 |
| Opus 5 | $0.00022 | $0.00346 |
| Sonnet 5 | $0.00009 | $0.00138 |
| Haiku 4.5 | $0.00004 | $0.00069 |
Grade A, and why
error-handling 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 4d 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Error Handling
Design resilient applications through intentional error handling strategies. Errors are data, not just exceptions — design them intentionally.
Quick Decision Guide
| Situation | Pattern | Reference |
|---|---|---|
| Typed error categories | Custom error classes | error-patterns.md |
| Explicit handling (no throws) | Result/Either type | error-patterns.md |
| React component crash | Error boundary | react-errors.md |
| API error response | Structured API errors | api-errors.md |
| Network calls that fail | Retry with backoff | recovery-patterns.md |
| Unreliable downstream service | Circuit breaker | recovery-patterns.md |
Key Principles
- Debuggable: Rich context, stack traces, correlation IDs
- Recoverable: Retry logic, fallbacks, circuit breakers
- User-friendly: Clear messages, recovery guidance, no leaked internals
- Consistent: Same error shape across all API endpoints
Quick Start Checklist
- Define base AppError class with code and context
- Create domain-specific error subclasses
- Implement consistent API error response shape
- Add error boundaries at app, route, and component levels
- Set up error tracking (Sentry) with scrubbing
References
| Reference | Description |
|---|---|
| error-patterns.md | Custom errors, Result types, error hierarchies |
| react-errors.md | Error boundaries, Suspense, React error handling |
| api-errors.md | HTTP errors, response shapes, status codes |
| recovery-patterns.md | Retry, circuit breaker, fallbacks, degradation |
| overview.md | Error types, Result pattern, user messages, tracking, anti-patterns |
| anti-rationalization.md | Iron Law, common rationalizations, red flag STOP list for error handling discipline |
| tdd-patterns.md | Test-first patterns for error paths, retry logic, boundaries |
| review-checklist.md | Error handling review checklist (classes, messages, recovery, tracking) |
What ships with it
8 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 53 lines · 43 tokens per session scan A ac0ce9ea9387
error-handling is a skill published in the GitHub repository srstomp/pokayokay (9 stars, last pushed 2mo ago), licensed MIT. It adds 43 tokens to every session and 692 once invoked, about $0.0002 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…