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/amadeus-dlc/amadeus/error-handlingnpx skills add amadeus-dlc/amadeus --skill error-handlinggit clone --depth 1 https://github.com/amadeus-dlc/amadeusWrote 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/amadeus-dlc/amadeus/error-handling)<a href="https://agentmods.dev/skills/amadeus-dlc/amadeus/error-handling"><img src="https://agentmods.dev/badge/skills/amadeus-dlc/amadeus/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.1 | $0.00066 | $0.00321 |
| Opus 5 | $0.00033 | $0.00161 |
| Sonnet 5 | $0.00013 | $0.00064 |
| Haiku 4.5 | $0.00007 | $0.00032 |
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 5d 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.
What it actually says
Error Handling
Choose error mechanisms by recoverability and caller responsibility.
Workflow
-
Classify each error as domain, validation, application, infrastructure, programming defect, or fatal system condition.
-
Use typed
Result/Either-style returns for recoverable domain and validation errors. -
Use exceptions or panics for defects and truly exceptional infrastructure failures when callers cannot make a local decision.
-
Preserve causal context without leaking secrets.
-
Put retry, timeout, and circuit-breaker policy at integration boundaries.
Rules
-
Domain errors should be explicit in function signatures where the language supports it.
-
Do not use exceptions for ordinary business branching.
-
Log once at the boundary that handles or reports the error.
-
Convert low-level errors into application-facing errors at layer boundaries.
Reference
Read references/guidelines.md for detailed patterns.
Detailed Reference
For non-trivial implementation, review, or refactoring work, read references/details.md before giving final guidance. It contains the detailed rules, examples, smells, and migration notes that do not belong in the short invocation body.
Output
Return the error taxonomy, mechanism choices, API changes, and tests.
What ships with it
2 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.
- 5d ago First seen · 44 lines · 66 tokens per session scan A 7ae5938e0485
error-handling is a skill published in the GitHub repository amadeus-dlc/amadeus (8 stars, last pushed 15d ago), licensed Apache-2.0. It adds 66 tokens to every session and 321 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
cocotrace
Build and query the SHA-256 requirements-to-implementation traceability graph across lifecycle artifacts.
cocoaudit
View and export the append-only session audit trail for regulated environments.
Changelog Test Mapper
Map changelog entries and release notes to affected test cases, ensuring every user-facing change has corresponding test coverage verification.
anti-monolith-guard
Prevent mixed-responsibility modules and uncontrolled file growth.
code-hygiene-refactor
Select a bounded, behavior-preserving code-hygiene batch.
agent-factory
Evidence-based gate for creating a new skill or agent profile.