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 paruff/uFawkesAI --skill unit-error-handlinggit clone --depth 1 https://github.com/paruff/uFawkesAIWrote 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/paruff/ufawkesai/unit-error-handling)<a href="https://agentmods.dev/skills/paruff/ufawkesai/unit-error-handling"><img src="https://agentmods.dev/badge/skills/paruff/ufawkesai/unit-error-handling/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/paruff/ufawkesai/unit-error-handling"><img src="https://agentmods.dev/badge/skills/paruff/ufawkesai/unit-error-handling.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.00039 | $0.00528 |
| Opus 5 | $0.00019 | $0.00264 |
| Sonnet 5 | $0.00008 | $0.00106 |
| Haiku 4.5 | $0.00004 | $0.00053 |
Grade A, and why
unit-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 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.
What it actually says
Skill: Unit Error Handling
Load trigger:
"load unit-error-handling skill"> DORA: Cap 5 (Operational Resilience) Token cost: Low
Purpose
Ensure predictable and safe error behavior across OBS and PIPE.
Responsibilities
- Validate thrown errors
- Validate error messages and codes
- Validate fallback logic
- Validate retry/backoff logic
- Validate invariant enforcement
Inputs
- Error scenarios
- Unit tests
Outputs
error-report.json
Error Categories
| Category | Test Focus | Example |
|---|---|---|
| Validation errors | thrown on bad input | Invalid YAML, missing fields |
| Network errors | retry behavior | Registry timeout, API failure |
| State errors | invariant enforcement | Invalid pipeline state |
| Resource errors | fallback logic | Missing file, unavailable service |
Error Test Patterns
// Validate error thrown
expect(() => parseVersion("invalid")).toThrow("Invalid version format");
// Validate error code
try {
await pullImage("nonexistent");
} catch (e) {
expect(e.code).toBe("IMAGE_NOT_FOUND");
}
// Validate retry backoff
const retrySpy = jest.spyOn(client, "retry");
await client.withRetry(() => failingCall());
expect(retrySpy).toHaveBeenCalledTimes(3);
Validation Rules
- All error paths tested
- No unhandled exceptions
- No silent failures
- Error messages descriptive
- Retry logic correct
Output Format
{
"skill": "unit-error-handling",
"status": "pass | fail",
"error_scenarios_tested": 25,
"unhandled_exceptions": 0,
"silent_failures": 0,
"retry_tests": {
"total": 5,
"passing": 5
}
}
Success Criteria
- All error paths tested
- No unhandled exceptions
- No silent failures
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 · 94 lines · 39 tokens per session scan A 91413961a83f
unit-error-handling is a skill published in the GitHub repository paruff/uFawkesAI (2 stars, last pushed 18d ago), licensed MIT. It adds 39 tokens to every session and 528 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-09-03.
Other skills, from other repositories
working-effectively-with-legacy-code
Apply Michael Feathers-inspired legacy-code rules when changing hard-to-test code safely with characterization tests, seams, sprout methods, or wrap methods.
refactoring-guru
Apply Refactoring.Guru-inspired rules when diagnosing code smells, choosing refactoring techniques, and stopping cleanup before uncontrolled redesign.
refactoring
Apply Martin Fowler-inspired refactoring rules when improving existing code structure while preserving observable behavior.
template-formal
Strongly-typed multiagent ant-robot colony exemplar — ADTs, session-typed protocols, affine-discipline resource handles, storage-as-functor framing, Active-Inference-flavored decision loop, mypy-as-oracle negative controls.
template-test-creation
Create pytest suites under the no-mocks policy — real data, temp files, subprocess, pytest-httpserver. USE WHEN adding tests, raising coverage, testing new src/ module, or user forbids mocks.
debug-issue
Structured workflow for debugging a reported or reproduced issue. Use when the user asks to debug a bug, find root cause, or fix a failing scenario.