Borrowing it
Nothing to install: this file belongs to DanielPodolsky/ownyourcode. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/DanielPodolsky/ownyourcode/main/.claude/skills/gates/error/SKILL.mdgit clone --depth 1 https://github.com/DanielPodolsky/ownyourcodeWrote 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/danielpodolsky/ownyourcode/error)<a href="https://agentmods.dev/skills/danielpodolsky/ownyourcode/error"><img src="https://agentmods.dev/badge/skills/danielpodolsky/ownyourcode/error/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/danielpodolsky/ownyourcode/error"><img src="https://agentmods.dev/badge/skills/danielpodolsky/ownyourcode/error.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00032 | $0.01357 |
| Opus 5.5 | $0.00013 | $0.00543 |
| Sonnet 5.5 | $0.00006 | $0.00271 |
| Haiku 4.5 | $0.00003 | $0.00136 |
Grade A, and why
error-handling-gate 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.
How it starts
The opening of the file, as written. The whole thing — 231 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Gate 3: Error Handling Review
"Happy path code is easy. Error handling is where senior engineers shine."
Purpose
This gate ensures the code handles failures gracefully, provides meaningful feedback to users, and doesn't silently swallow errors.
Gate Status
- PASS — Error handling is appropriate
- WARNING — Issues found that should be addressed
Gate Questions
Question 1: Failure Scenario
"What happens if [main operation] fails? Walk me through the user experience."
Looking for:
- Awareness of failure modes
- User-friendly error messages
- Recovery options (retry, fallback)
- No silent failures
Example scenarios:
- Network request fails
- Database is down
- Validation fails
- Third-party API errors
Question 2: User Feedback
"What does the user see when an error occurs? Would they understand what to do next?"
Looking for:
- Helpful, non-technical messages
- Actionable guidance ("Try again", "Check your connection")
- Appropriate error placement in UI
Question 3: Error Visibility
"How would you debug this in production if something went wrong?"
Looking for:
- Errors are logged
- Sufficient context in logs
- No sensitive data in logs
- Error tracking awareness (Sentry, etc.)
Error Handling Checklist
Async Operations
- All async calls wrapped in try/catch or .catch()
- No empty catch blocks
- Errors include context (what operation, what data)
- finally blocks for cleanup (loading states, etc.)
User Experience
- User-friendly error messages (no technical jargon)
- Errors are actionable (what can user do?)
- Loading states cleared on error
- Retry options where appropriate
Logging & Debugging
- Errors logged with context
- No sensitive data in error logs
- Error types/codes for categorization
- Stack traces available in development
Edge Cases
- Empty states handled
- Timeout handling
- Partial failure handling (some items succeed, some fail)
- Concurrent request handling
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 · 231 lines · 32 tokens per session scan A 0583a04cc9d6
error-handling-gate is a skill published in the GitHub repository DanielPodolsky/ownyourcode (292 stars, last pushed 4mo ago), licensed MIT. It adds 32 tokens to every session and 1,357 once invoked, about $0.0001 per session on Opus 5.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-30.
Other skills, from other repositories
Verification & Quality Assurance
Comprehensive truth scoring, code quality verification, and automatic rollback system with 0.95 accuracy threshold for ensuring high-quality agent outputs and codebase reliability.
mcp-app-verification
Comprehensive verification checklists for MCP Apps. Tests with basic-host reference, validates handler-before-connect, text fallback, resource URI linking, single-file bundling, host styling, CSP, and legacy pattern detection.
quality-hooks
Language-specific auto-lint/format/typecheck pipeline. Supports Python (ruff+pyright), TypeScript (prettier+eslint+tsc), Go (gofmt+golangci-lint). Auto-fix and convergence loops.
xcode-workflows
Xcode build system guidance for xcodebuild operations. Use when building iOS projects, running tests, analyzing build failures, or configuring schemes. Covers build/clean/test operations, interpreting xcodebuild output, and troubleshooting common build errors.
hook-management
Session-scoped hook lifecycle management with enable/disable/status controls, execution profiling, and color-coded performance alerts.
spec-execution
6-phase iterative specification execution workflow covering implementation, testing, review, improvement, commit, and progress tracking with quality-gated convergence.