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 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/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/ivegamsft/basecoat/api-design"><img src="https://agentmods.dev/badge/skills/ivegamsft/basecoat/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.00076 | $0.00305 |
| Opus 5.5 | $0.00030 | $0.00122 |
| Sonnet 5.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 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
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.
- 1mo 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 10d ago), licensed MIT. It adds 76 tokens to every session and 305 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
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…
api-design-patterns
Comprehensive API design patterns covering REST, GraphQL, gRPC, versioning, authentication, and modern API best practices.
architecture-patterns
Software architecture patterns and best practices.
dotnet-aspnetcore-service
Use when building or extending a C# service on ASP.NET Core - Minimal APIs or controllers, DI and options, EF Core with Npgsql, ProblemDetails, HttpClientFactory resilience, async and cancellation.
node-typescript-service
Use when building or extending a TypeScript service on Node.js - Fastify, NestJS, Express or Hono, runtime validation at the boundary, strict types, the repository's ORM and migrations, async error handling, graceful shutdown.
rust-axum-service
Use when building or extending a Rust service - axum on tokio (or the repository's actix-web / rocket), typed errors with IntoResponse, serde at the boundary, sqlx queries and migrations, never blocking the runtime, tracing, clippy.