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 New1Direction/korgex --skill api-designgit clone --depth 1 https://github.com/New1Direction/korgexWrote 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/new1direction/korgex/api-design)<a href="https://agentmods.dev/skills/new1direction/korgex/api-design"><img src="https://agentmods.dev/badge/skills/new1direction/korgex/api-design/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/new1direction/korgex/api-design"><img src="https://agentmods.dev/badge/skills/new1direction/korgex/api-design.svg" alt="Reviewed on agentmods" width="80" 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.00017 | $0.00345 |
| Opus 5.5 | $0.00007 | $0.00138 |
| Sonnet 5.5 | $0.00003 | $0.00069 |
| Haiku 4.5 | $0.00002 | $0.00034 |
Grade A, and why
api-design 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.
What it actually says
An API (a function, module, endpoint, or library surface) is a contract others depend on. Design the smallest, clearest one that does the job.
- Start from the caller. Write the usage you wish existed first. If it reads well and the obvious call is the correct one, the design is good.
- Make it hard to misuse. Prefer types/enums over stringly-typed flags; make illegal states unrepresentable; require the essential args, default the rest. The easy path should be the safe path.
- Keep the surface small. Expose the minimum; hide internals. Every public name is a future maintenance promise. Fewer, well-named entry points beat many overlapping ones.
- Be consistent. Match the naming, argument order, and error conventions of the surrounding code so callers can predict it.
- Define the contract: inputs, outputs, errors/failure modes, and side effects. Decide how errors surface (exception vs result) and be uniform.
- Design for change. Additive evolution (new optional params, new functions) over breaking signatures. If you must break, version it and migrate (see database-migrations / breaking-change discipline).
- YAGNI. Don't add parameters or extension points "just in case" — they're surface you'll maintain forever. Add them when a real caller needs them.
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 · 28 lines · 17 tokens per session scan A 696a966bdf37
api-design is a skill published in the GitHub repository New1Direction/korgex (5 stars, last pushed 4d ago), licensed MIT. It adds 17 tokens to every session and 345 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-31.
Other skills, from other repositories
api-contract-reviewer
Conditional code-review persona, selected when the diff touches API routes, request/response types, serialization, versioning, or exported type signatures. Reviews code for breaking contract changes. Spawned by the ce:review-beta skill as part of a reviewer ensemble.
dhh-rails-reviewer
Brutally honest Rails code review from DHH's perspective. Use when reviewing Rails code for anti-patterns, JS framework contamination, or violations of Rails conventions.
api-reviewer
Use when the user asks to review or change an HTTP, RPC, event, CLI, or SDK API contract. Inspect routes, schemas, authorization, errors, compatibility, and consumers before editing, then verify request and response behavior with focused tests.
vibe-security
A defensive security review workflow for code, dependencies, and application configuration. It checks for vulnerabilities such as unsafe input handling, unauthorized access, exposed sensitive data, and known problems in installed packages.
api-design
REST API design patterns — naming, versioning, error handling, pagination, authentication.
vibe-api-docs
Use this skill to generate and maintain detailed API documentation based on frontend/backend needs.