route_definition

route_definition is a skill for Claude Code, Codex from jkaninda/okapi-skills. It costs 0 tokens per session (2,518 once invoked), scanned A, original, MIT.

A struct-based way to define API routes instead of registering them through separate method calls. A route definition keeps its method, path, handler, middleware group, and documentation details together.

In plain words
What is it for?
Use it to register routes programmatically and attach OpenAPI details such as operation IDs, summaries, tags, request schemas, and response schemas.
Why use it?
It makes routes easier to read, move between files, and generate from data because the route's behavior and metadata live in one declared object.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to register routes programmatically and attach OpenAPI details such as operation IDs, summaries, tags, request schemas, and response schemas.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jkaninda/okapi-skills/route_definition
Install

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.

Any agent
npx skills add jkaninda/okapi-skills --skill route_definition
Clone the repo
git clone --depth 1 https://github.com/jkaninda/okapi-skills

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for route_definition

README.md
[![agentmods](https://agentmods.dev/badge/skills/jkaninda/okapi-skills/route_definition/github.svg)](https://agentmods.dev/skills/jkaninda/okapi-skills/route_definition)
Your own site
<a href="https://agentmods.dev/skills/jkaninda/okapi-skills/route_definition"><img src="https://agentmods.dev/badge/skills/jkaninda/okapi-skills/route_definition/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.

agentmods 80×15 button for route_definition

Your own site · 80×15
<a href="https://agentmods.dev/skills/jkaninda/okapi-skills/route_definition"><img src="https://agentmods.dev/badge/skills/jkaninda/okapi-skills/route_definition.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,518 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.02518
Opus 5 $0.00000 $0.01259
Sonnet 5 $0.00000 $0.00504
Haiku 4.5 $0.00000 $0.00252

Measured 10d ago against content hash 6db3e3d17dd9, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

route_definition 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 10d 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.

route_definition/SKILL.md · 267 lines

How it starts

The opening of the file, as written. The whole thing — 267 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Okapi Route Definition Skills

Okapi's RouteDefinition is a declarative alternative to imperative route registration (.Get(), .Post(), etc.). Instead of chaining method calls, you describe each route as a struct and register it with app.Register(). This keeps route metadata — method, path, handler, documentation, middleware — in one place, making routes easier to read, move between files, and generate programmatically.

RouteDefinition Struct

Field Type Description
Method string HTTP method (http.MethodGet, http.MethodPost, etc.)
Path string Route path relative to its group (e.g. "/books/{id:int}")
Handler okapi.HandlerFunc Handler function — use okapi.H() for generic input binding
Group *okapi.Group Group this route belongs to (prefix, middleware, tags)
OperationId string OpenAPI operation ID
Summary string Short description for OpenAPI docs
Description string Detailed description for OpenAPI docs
Tags []string OpenAPI tags (overrides group tags if set)
Request any Request body schema for OpenAPI docs
Response any Success response schema (defaults to 200)
Security []map[string][]string OpenAPI security requirements
Options []okapi.RouteOption Additional route options (error responses, path params, etc.)
Middlewares []okapi.Middleware Per-route middleware

Read the full file on GitHub · 267 lines

Changes

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.

  1. 10d ago First seen · 267 lines · 0 tokens per session scan A 6db3e3d17dd9

Subscribe to this mod's changes

route_definition is a skill published in the GitHub repository jkaninda/okapi-skills (3 stars, last pushed 24d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,518 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.

Related

Other skills, from other repositories

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.

seb1n/awesome-ai-agent-skills · 53 tokens

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.

seb1n/awesome-ai-agent-skills · 47 tokens

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.

seb1n/awesome-ai-agent-skills · 48 tokens

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.

seb1n/awesome-ai-agent-skills · 45 tokens

model-deployment

Deploy trained machine learning models as production-ready services using REST APIs, containers, serverless functions, and orchestration platforms. Use when the user requests model deployment or provides relevant inputs for this workflow.

seb1n/awesome-ai-agent-skills · 43 tokens

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.

seb1n/awesome-ai-agent-skills · 42 tokens