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 saajunaid/caddis-plugin --skill api-designgit clone --depth 1 https://github.com/saajunaid/caddis-pluginWrote 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/saajunaid/caddis-plugin/api-design)<a href="https://agentmods.dev/skills/saajunaid/caddis-plugin/api-design"><img src="https://agentmods.dev/badge/skills/saajunaid/caddis-plugin/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/saajunaid/caddis-plugin/api-design"><img src="https://agentmods.dev/badge/skills/saajunaid/caddis-plugin/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.00034 | $0.01931 |
| Opus 5.5 | $0.00014 | $0.00772 |
| Sonnet 5.5 | $0.00007 | $0.00386 |
| Haiku 4.5 | $0.00003 | $0.00193 |
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 17d 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.
API Design Skill
Design APIs that are consistent, discoverable, and hard to misuse. Conventions over configuration.
1. When to Apply This Skill
Trigger conditions:
- Designing new API endpoints or a full API surface
- "What should this endpoint look like?"
- Planning API versioning or migration
- Reviewing API contracts for consistency
- Building an API spec or OpenAPI document
2. REST Resource Naming
URL Convention
# Resources are nouns, plural, lowercase, kebab-case
GET /api/v1/customers # List
GET /api/v1/customers/{id} # Get one
POST /api/v1/customers # Create
PUT /api/v1/customers/{id} # Full update
PATCH /api/v1/customers/{id} # Partial update
DELETE /api/v1/customers/{id} # Delete
# Nested resources for strong ownership
GET /api/v1/customers/{id}/orders # Customer's orders
POST /api/v1/customers/{id}/orders # Create order for customer
# Actions (when CRUD doesn't fit) — verb suffix
POST /api/v1/orders/{id}/cancel # Action on resource
POST /api/v1/reports/generate # Trigger async operation
Naming Rules
| Rule | Good | Bad |
|---|---|---|
| Plural nouns | /customers |
/customer, /getCustomers |
| Kebab-case | /order-items |
/orderItems, /order_items |
| No verbs in path | /customers (POST = create) |
/createCustomer |
| Consistent nesting depth | Max 2 levels: /customers/{id}/orders |
/customers/{id}/orders/{id}/items/{id}/details |
| No trailing slash | /customers |
/customers/ |
3. Request & Response Envelope
Success Response
{
"data": { ... },
"meta": {
"request_id": "req_abc123",
"timestamp": "2025-01-15T10:30:00Z"
}
}
List Response (with pagination)
{
"data": [ ... ],
"pagination": {
"page": 1,
"per_page": 25,
"total": 142,
"total_pages": 6
}
}
Error Response
{
"error": {
"code": "VALIDATION_ERROR",
"message": "Request validation failed",
"details": [
{ "field": "email", "message": "Invalid email format" },
{ "field": "age", "message": "Must be at least 18" }
]
}
}
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.
- 17d ago Changed · -14 tokens per session ffb1bbd72f2b
- 1mo ago First seen · 250 lines · 48 tokens per session scan A 2e3d4f810e6e
api-design is a skill published in the GitHub repository saajunaid/caddis-plugin (0 stars, last pushed today), licensed MIT. It adds 34 tokens to every session and 1,931 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-09-03.
Other skills, from other repositories
agent-raft-manager
Agent skill for raft-manager - invoke with $agent-raft-manager.
moai-ref-api-patterns
REST/GraphQL API design patterns, error handling conventions, and input validation reference for backend development. Agent-extending skill that amplifies backend domain work (spawned via Agent(general-purpose) with backend instructions) with production-grade API patterns. Use when designing APIs, implementing…
continuum-tools-mcp
Connect MCP servers (Stdio/SSE/StreamableHTTP) to a Continuum agent, configure tool filtering, set up tool-context capture/injection (e.g. sessionid), and read run artifacts (UI widgets, structured tool data). Invoke when the user asks "connect MCP", "filesystem tool", "remote API tool", "auto-capture sessionid"…
goga-define-challenge
Challenge the complete product definition before the PRD is generated.
goga-define-goals
Define the product outcomes that should be achieved by solving the identified problem for the relevant users.
goga-prototype-contracts
Designing usages and annotations per cell for the prototype pipeline.