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 jkaninda/okapi-skills --skill error_handlinggit clone --depth 1 https://github.com/jkaninda/okapi-skillsWrote 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/jkaninda/okapi-skills/error_handling)<a href="https://agentmods.dev/skills/jkaninda/okapi-skills/error_handling"><img src="https://agentmods.dev/badge/skills/jkaninda/okapi-skills/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.00000 | $0.02068 |
| Opus 5 | $0.00000 | $0.01034 |
| Sonnet 5 | $0.00000 | $0.00414 |
| Haiku 4.5 | $0.00000 | $0.00207 |
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 7d 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 — 242 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Okapi Error Handling
Handlers return error. The Abort* helpers write a response through the configured ErrorHandler and return an error you propagate; the Error* helpers write a fixed JSON envelope directly, bypassing the handler. Three formats ship in the box: the default JSON envelope, a fully custom handler, and RFC 7807 Problem Details.
Aborting from a Handler
o.Post("/books", func(c *okapi.Context) error {
book := &Book{}
if err := c.Bind(book); err != nil {
return c.AbortBadRequest("Invalid request body", err)
}
return c.Created(book)
})
Default response body (okapi.ErrorResponse):
{
"code": 400,
"message": "Invalid request body",
"details": "field Name is required",
"timestamp": "2026-08-16T21:34:17+01:00"
}
Always propagate the returned error (return c.AbortX(...)). Writing another body afterwards is a no-op — see "Write-Once Semantics" in the response/ skill.
Abort Methods
Signature: c.AbortXxx(msg string, err ...error) error. All route through the configured error handler.
4xx
| Method | Status |
|---|---|
AbortBadRequest |
400 |
AbortUnauthorized |
401 |
AbortPaymentRequired |
402 |
AbortForbidden |
403 |
AbortNotFound |
404 |
AbortMethodNotAllowed |
405 |
AbortNotAcceptable |
406 |
AbortProxyAuthRequired |
407 |
AbortRequestTimeout |
408 |
AbortConflict |
409 |
AbortGone |
410 |
AbortLengthRequired |
411 |
AbortPreconditionFailed |
412 |
AbortRequestEntityTooLarge |
413 |
AbortRequestURITooLong |
414 |
AbortUnsupportedMediaType |
415 |
AbortRequestedRangeNotSatisfiable |
416 |
AbortExpectationFailed |
417 |
AbortTeapot |
418 |
AbortMisdirectedRequest |
421 |
AbortValidationError |
422 |
AbortLocked |
423 |
AbortFailedDependency |
424 |
AbortTooEarly |
425 |
AbortUpgradeRequired |
426 |
AbortPreconditionRequired |
428 |
AbortTooManyRequests |
429 |
AbortRequestHeaderFieldsTooLarge |
431 |
AbortUnavailableForLegalReasons |
451 |
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.
- 7d ago First seen · 242 lines · 0 tokens per session scan A 0e37a9337c2b
error_handling is a skill published in the GitHub repository jkaninda/okapi-skills (3 stars, last pushed 22d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,068 tokens. 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
webhook-setup
Set up webhook receivers with signature verification, idempotent event processing, retry handling, and dead letter queues for reliable event-driven integrations. Use when the user requests webhook setup or provides relevant inputs for this workflow.
api-integration
Integrate with external APIs using REST clients, webhook consumers, SDK wrappers, and polling patterns with proper authentication, error handling, and retry logic. Use when the user requests api integration or provides relevant inputs for this workflow.
graphql-api-design
Design GraphQL APIs with well-structured schemas, efficient resolvers, pagination, and performance patterns like DataLoader and federation. Use when the user requests graphql api design or provides relevant inputs for this workflow.
oauth-2-0-setup
Implement OAuth 2.0 authentication flows including authorization code with PKCE, client credentials, and device code for secure API integration. Use when the user requests oauth 2 0 setup or provides relevant inputs for this workflow.
api-design
Design RESTful APIs with proper resource modeling, HTTP method semantics, status codes, pagination, versioning, and documentation. Use when the user requests api design or provides relevant inputs for this workflow.
dynamic-application-security-testing
Perform dynamic security testing against running web applications and APIs to discover vulnerabilities through active probing and fuzzing. Use when the user requests dynamic application security testing or provides relevant inputs for this workflow.