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/ivegamsft/basecoat/api-designnpx skills add ivegamsft/basecoat --skill api-designgit clone --depth 1 https://github.com/ivegamsft/basecoatWrote 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/ivegamsft/basecoat/api-design)<a href="https://agentmods.dev/skills/ivegamsft/basecoat/api-design"><img src="https://agentmods.dev/badge/skills/ivegamsft/basecoat/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.1 | $0.00076 | $0.00305 |
| Opus 5 | $0.00038 | $0.00152 |
| Sonnet 5 | $0.00015 | $0.00061 |
| Haiku 4.5 | $0.00008 | $0.00030 |
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 3d 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
API Design Skill
Design new API contracts, review spec changes for breaking changes, choose versioning strategies, and enforce API governance standards.
Templates in This Skill
| Template | Purpose |
|---|---|
openapi-template.md |
OpenAPI 3.x skeleton for a new REST API resource with CRUD, pagination, and error envelopes |
breaking-change-checklist.md |
Checklist for evaluating whether a spec change is breaking, with mitigation guidance |
versioning-decision-tree.md |
Decision tree for choosing the right versioning action for a given change |
api-governance-checklist.md |
Governance checklist every API spec must pass before approval |
Agent Pairing
Use with api-designer agent. For implementation hand off to backend-dev; for data models coordinate with data-tier; share the spec with frontend-dev for consumer integration.
What ships with it
5 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.
- 3d ago First seen · 29 lines · 76 tokens per session scan A a62b13a478ff
api-design is a skill published in the GitHub repository ivegamsft/basecoat (4 stars, last pushed 2d ago), licensed MIT. It adds 76 tokens to every session and 305 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
architecture-decision-record
ADR templates in the Nygard format with context, decision, consequences, and alternatives. Use when writing ADRs, recording an architectural decision, or evaluating options.
frontmcp-guides
Tutorials, end-to-end walkthroughs, and complete reference projects for FrontMCP. Use when you want a getting-started guide, a full worked example, or to learn best practices by following a step-by-step build rather than a single API reference. Includes a beginner weather-API server (tool plus static resource, Zod…
architecture-paradigm-domain-driven
Models a business in its own language. Use when the domain has real business rules to capture.
architecture-paradigm-microservices
Applies microservices for independent deployment and per-service scaling. Use when teams need autonomous release cycles with distinct capability scaling needs.
architecture-paradigm-functional-core
Applies Functional Core, Imperative Shell to isolate logic from side effects. Use when business logic is entangled with I/O or unit tests are slow and brittle.
architecture-paradigm-hexagonal
Applies hexagonal architecture isolating domain from infrastructure. Use when designing systems where testability and port/adapter separation are priorities.