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/danielpodolsky/ownyourcode/errornpx skills add DanielPodolsky/ownyourcode --skill errorgit clone --depth 1 https://github.com/DanielPodolsky/ownyourcodeWhat 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.00032 | $0.01357 |
| Opus 5 | $0.00016 | $0.00678 |
| Sonnet 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 yesterday.
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.
- yesterday First seen · 231 lines · 32 tokens per session scan A 0583a04cc9d6
error-handling-gate is a skill published in the GitHub repository DanielPodolsky/ownyourcode (276 stars, last pushed 2mo ago), licensed MIT. It adds 32 tokens to every session and 1,357 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-30.
Other skills, from other repositories
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
agent-code-analyzer
Agent skill for code-analyzer - invoke with $agent-code-analyzer.
agui-dotnet-streaming-chat
Get started with the AG-UI .NET SDK: bootstrap and run your first streaming-chat app (client + server) with the AG-UI .NET NuGet packages (AGUI.Client, AGUI.Server, AGUI.Formatting, AGUI.Abstractions). USE FOR: which packages to install and how to wire them; constructing an AGUIChatClient against an endpoint and…
agui-dotnet-sample-step
Add a GettingStarted sample Step (a Server/Client pair) to the AG-UI .NET SDK that demonstrates one protocol feature the way we want users to write it. USE FOR: adding a new samples/GettingStarted/StepNN Server+Client pair, wiring it into AGUI.slnx and the integration-test project, giving it a deterministic…
agui-dotnet-protobuf
Use the protobuf wire transport (instead of the default Server-Sent Events) for an AG-UI connection with the AG-UI .NET SDK — a compact binary event stream negotiated via the Accept header. USE FOR: making an AGUIChatClient prefer protobuf by wiring an AGUIEventStreamHandler with ProtobufEventStreamFormatter (then…
github-pr-description
Generate and create pull request descriptions automatically using GitHub CLI. Use when the user asks to create a PR, generate a PR description, make a pull request, or submit changes for review. Analyzes git diff and commit history to create comprehensive, meaningful PR descriptions that explain what changed, why it…