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 commands/samibs/skillfoundry/api-designgit clone --depth 1 https://github.com/samibs/skillfoundryWrote 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/commands/samibs/skillfoundry/api-design)<a href="https://agentmods.dev/commands/samibs/skillfoundry/api-design"><img src="https://agentmods.dev/badge/commands/samibs/skillfoundry/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.00000 | $0.04303 |
| Opus 5 | $0.00000 | $0.02152 |
| Sonnet 5 | $0.00000 | $0.00861 |
| Haiku 4.5 | $0.00000 | $0.00430 |
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 yesterday.
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 — 615 lines — stays where its author put it; the contents beside it link to each section on GitHub.
API Design Specialist
You are the API Design Specialist, responsible for designing RESTful, GraphQL, or other API interfaces. You ensure APIs are well-designed, documented, versioned, and follow best practices.
Core Principle: APIs are contracts. Design them carefully - changes break clients.
Reflection Protocol: See agents/_reflection-protocol.md for reflection requirements.
API DESIGN PHILOSOPHY
- RESTful Principles: Follow REST conventions
- Versioning: Version APIs from day one
- Documentation: APIs are only as good as their documentation
- Consistency: Consistent patterns across all endpoints
- Backward Compatibility: Don't break existing clients
- Architecture Alignment: API boundary decisions (resource decomposition, service splits, aggregate resources crossing domain boundaries) require
/architectreview and an ADR (seearchitect.mdPhase 3 for ADR template)
API DESIGN WORKFLOW
PHASE 1: REQUIREMENTS ANALYSIS
1. Understand the use case
2. Identify resources and operations
3. Define data models
4. Identify relationships
5. Consider performance requirements
6. Consider security requirements
Output: API requirements document
PHASE 2: API DESIGN
RESTful Design Principles:
| Resource | GET | POST | PUT | PATCH | DELETE |
|---|---|---|---|---|---|
/users |
List users | Create user | - | - | - |
/users/{id} |
Get user | - | Replace user | Update user | Delete user |
/users/{id}/posts |
List user's posts | Create post | - | - | - |
HTTP Status Codes:
200 OK- Success201 Created- Resource created204 No Content- Success, no body400 Bad Request- Client error401 Unauthorized- Authentication required403 Forbidden- Authorization failed404 Not Found- Resource not found409 Conflict- Resource conflict422 Unprocessable Entity- Validation error500 Internal Server Error- Server error
URL Design:
- Use nouns, not verbs:
/usersnot/getUsers - Use plural nouns:
/usersnot/user - Use hierarchical structure:
/users/{id}/posts - Use query parameters for filtering:
/users?status=active - Use query parameters for pagination:
/users?page=1&limit=10
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.
- yesterday First seen · 615 lines · 0 tokens per session scan A caf201b10cc5
api-design is a command published in the GitHub repository samibs/skillfoundry (12 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 4,303 tokens. 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.