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/jkaninda/okapi-skills/openapinpx skills add jkaninda/okapi-skills --skill openapigit 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/openapi)<a href="https://agentmods.dev/skills/jkaninda/okapi-skills/openapi"><img src="https://agentmods.dev/badge/skills/jkaninda/okapi-skills/openapi.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 | $0.00000 | $0.02499 |
| Opus 5 | $0.00000 | $0.01249 |
| Sonnet 5 | $0.00000 | $0.00500 |
| Haiku 4.5 | $0.00000 | $0.00250 |
Grade A, and why
openapi 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 4d 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 — 250 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Okapi OpenAPI Documentation
Okapi generates OpenAPI from your routes and serves three interactive UIs. The default document is OpenAPI 3.1 (JSON Schema 2020-12); a 3.0 view is served alongside for legacy consumers.
Default Endpoints
| Route | Content |
|---|---|
/docs |
Selected UI (Swagger UI by default) |
/swagger |
Swagger UI |
/redoc |
ReDoc |
/scalar |
Scalar API Reference |
/openapi.json |
OpenAPI 3.1 spec (JSON) |
/openapi.yaml |
OpenAPI 3.1 spec (YAML) |
/openapi-3.0.json |
OpenAPI 3.0 spec (JSON) |
/openapi-3.0.yaml |
OpenAPI 3.0 spec (YAML) |
Enabling Docs
o := okapi.Default() // docs ON by default
o := okapi.New().WithOpenAPIDocs() // opt in for New()
o.WithOpenAPIDisabled() // disable (routes return 404)
The document is rebuilt lazily, so route changes (enable/disable, new webhooks) show up on the next request.
Choosing the UI
o.WithOpenAPIDocs(okapi.OpenAPI{
Title: "My API",
UI: okapi.ScalarUI, // SwaggerUI (default) | RedocUI | ScalarUI
})
// Chainable equivalent
o := okapi.New().WithOpenAPIDocs().WithDocUI(okapi.ScalarUI)
// Or as an option: okapi.New(okapi.WithDocUI(okapi.RedocUI))
Every UI stays reachable at its own route. StrictDocUI: true registers only /docs; the per-UI routes then 404:
o.WithOpenAPIDocs(okapi.OpenAPI{
Title: "My API",
UI: okapi.ScalarUI,
StrictDocUI: true,
})
Full Configuration
o.WithOpenAPIDocs(okapi.OpenAPI{
Title: "Example API",
Version: "1.0.0",
Summary: "Short summary", // OpenAPI >= 3.1 only
Description: "Example API description",
TermsOfService: "https://example.com/terms",
Favicon: "https://example.com/favicon.png", // favicon for the doc UIs
Servers: okapi.Servers{{URL: "https://api.example.com", Description: "Production"}},
License: okapi.License{Name: "Apache 2.0", Identifier: "Apache-2.0"}, // SPDX → 3.1 only
Contact: okapi.Contact{Name: "API Support", Email: "[email protected]", URL: "https://example.com"},
ExternalDocs: &okapi.ExternalDocs{URL: "https://docs.example.com", Description: "Docs"},
SecuritySchemes: okapi.SecuritySchemes{
{Name: "basicAuth", Type: "http", Scheme: "basic"},
{Name: "bearerAuth", Type: "http", Scheme: "bearer", BearerFormat: "JWT"},
{Name: "apiKey", Type: "apiKey", In: "header", Description: "API key header"},
{
Name: "OAuth2", Type: "oauth2",
Flows: &okapi.OAuthFlows{
AuthorizationCode: &okapi.OAuthFlow{
AuthorizationURL: "https://auth.example.com/authorize",
TokenURL: "https://auth.example.com/token",
RefreshURL: "https://auth.example.com/refresh",
Scopes: map[string]string{"read": "Read access", "write": "Write access"},
},
},
},
},
})
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.
- 4d ago First seen · 250 lines · 0 tokens per session scan A e1fb04074702
openapi is a skill published in the GitHub repository jkaninda/okapi-skills (3 stars, last pushed 19d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,499 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
cross-border-ecommerce
Cross-border e-commerce expansion advisor. Scores target markets on 8 weighted dimensions (market size, ecommerce penetration, competition, regulatory complexity, logistics infrastructure, payment ecosystem, cultural distance, IP protection), compares 5 fulfillment models with cost and transit data, provides…
ecommerce-email-marketing-builder
E-commerce email marketing system builder. Creates complete email automation flows with full copywriting, subject lines, ESP setup instructions, segmentation rules, and annual campaign calendars. Generates copy-paste-ready email sequences for Klaviyo, Omnisend, Mailchimp, or any ESP. Covers welcome series, cart…
ecommerce-growth-strategy
E-commerce growth strategy advisor. Diagnoses current business health using unit economics (CAC, LTV, AOV, contribution margin), identifies the highest-impact growth opportunities across 5 levers (traffic, conversion, AOV, retention, expansion), and builds a prioritized 90-day growth roadmap. Uses the Ansoff Matrix…
ecommerce-ppc-strategy-planner
Cross-platform PPC strategy planner for ecommerce businesses. Analyzes your product and margins, recommends the right advertising platforms (Google Ads, Meta Ads, TikTok Ads), calculates ROAS targets, allocates budget across channels, and generates platform-specific campaign briefs with ad copy and creative direction.…
ecommerce-marketing-strategy-builder
Full-stack e-commerce marketing strategy builder. Analyzes your product, market, and competitors, then builds a complete omnichannel marketing plan covering paid ads, SEO, email/SMS, content marketing, social media, influencer partnerships, and referral programs. Includes target audience persona, competitive…
ecommerce-social-media-marketing
Social media marketing strategy for ecommerce brands. Content calendar planning, platform-specific strategies, social commerce optimization, influencer collaboration, and community building. Use when the user asks about social media marketing, social commerce, content strategy, or social media for ecommerce.