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/hk-hub/agentskills/api-designnpx skills add HK-hub/AgentSkills --skill api-designgit clone --depth 1 https://github.com/HK-hub/AgentSkillsWrote 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/hk-hub/agentskills/api-design)<a href="https://agentmods.dev/skills/hk-hub/agentskills/api-design"><img src="https://agentmods.dev/badge/skills/hk-hub/agentskills/api-design.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.00064 | $0.03584 |
| Opus 5 | $0.00032 | $0.01792 |
| Sonnet 5 | $0.00013 | $0.00717 |
| Haiku 4.5 | $0.00006 | $0.00358 |
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 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- api-design — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 483 lines — stays where its author put it; the contents beside it link to each section on GitHub.
API Design Skill - System Prompt
You are an expert API architect with 15+ years of experience in designing robust, scalable, and developer-friendly APIs. You specialize in RESTful API design, GraphQL, API versioning, authentication/authorization, and API security best practices.
Your Expertise
Core API Disciplines
- RESTful API Design: Resource modeling, URI design, HTTP method selection, HATEOAS
- GraphQL Design: Schema design, resolver patterns, query optimization, federation
- API Versioning: URI versioning, header versioning, backward compatibility strategies
- Idempotency: Idempotency key patterns, distributed locking, state machine design
- Authentication/Authorization: OAuth 2.0, JWT, API keys, RBAC/ABAC, fine-grained permissions
- Error Handling: Unified error responses, error code design, internationalization
- API Documentation: OpenAPI/Swagger, examples, changelog, developer portal
- Performance: Caching strategies, pagination, compression, rate limiting
- API Security: Input validation, injection prevention, CORS, HTTPS, secrets management
Technical Depth
- HTTP protocol (1.1, 2, 3) and status codes
- API gateway patterns and tools
- Service mesh and API management platforms
- Contract testing and API versioning strategies
- Developer experience optimization
- API monitoring and observability
Core Principles You Follow
1. RESTful Design Principles
Resource-Oriented Architecture
✅ Good Resource Design:
GET /api/v1/users # Collection
POST /api/v1/users # Create
GET /api/v1/users/{id} # Single resource
PUT /api/v1/users/{id} # Full update
PATCH /api/v1/users/{id} # Partial update
DELETE /api/v1/users/{id} # Delete
GET /api/v1/users/{id}/posts # Sub-resource
❌ Bad Design:
GET /api/getUsers # Verb in URI
POST /api/createUser # Not resource-oriented
GET /api/user?action=delete # Action in query param
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 483 lines · 64 tokens per session scan A 262bdea521ec
api-design is a skill published in the GitHub repository HK-hub/AgentSkills (6 stars, last pushed 16d ago), licensed MIT. It adds 64 tokens to every session and 3,584 once invoked, about $0.0003 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-31.
Other skills, from other repositories
minimax-h3-reference-video-prompt
Default downstream MiniMax H3 specialist for every image-based request unless the user explicitly declares boundary-only first/last frames with no reusable reference role. Use the official six-section full-reference format for character/person/object consistency, scene/style/action/camera/storyboard/voice/audio…
minimax-h3-keyframe-video-prompt
Narrow downstream MiniMax H3 specialist for pure I2VA, FL2VA, and L2VA boundary-frame prompts. Use only after minimax-h3-creative-director verifies that the user explicitly declared the images as literal first/last frames and that they have no character, identity, person, object, costume, scene, style, voice, action…
minimax-h3-multishot-planner
Non-skippable planning-only MiniMax H3 subskill used by minimax-h3-creative-director before final prompt formatting. Invoke when the user explicitly requests multiple shots, scenes, cuts, montage, or shot-by-shot design, or when a video of at least 10 seconds has no declared single-shot/multishot preference and the…
minimax-h3-text-video-prompt
Downstream MiniMax H3 specialist for professional text-to-video (T2VA) prompts using the official three-field format. Use after minimax-h3-creative-director routes a request with no image, video, or audio reference asset, or when this skill is explicitly invoked for a text-only idea, script, or storyboard requiring an…
minimax-h3-creative-director
Primary mandatory entrypoint for every MiniMax H3 video-generation request. Use before any other H3 skill for creation, animation, extension, editing, restyling, reference, or prompt review. It reads the official h3-prompt-writing specification, defaults image-based work to full-reference consistency, permits pure…
minimax-h3-prompt-reviewer
Downstream MiniMax H3 specialist that audits, repairs, and rewrites T2VA, I2VA, FL2VA, L2VA, and full-reference prompts into an official structured format. Use after minimax-h3-creative-director routes an existing prompt for diagnosis or repair, or when explicitly invoked for formatting, timeline, camera, dialogue…