api-design

Guidelines for designing interfaces that software uses to communicate, such as REST or GraphQL APIs. They treat an API as a documented contract between programs.

In plain words
What is it for?
Use them to plan resources, operations, data models, security, documentation, versioning, and compatibility for an API.
Why use it?
They help prevent inconsistent endpoints and changes that break existing users or applications.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/samibs/skillfoundry/api-design
Any agent
npx skills add samibs/skillfoundry --skill api-design
Clone the repo
git clone --depth 1 https://github.com/samibs/skillfoundry

Made for: Claude Code, Codex.

Per session 6 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,319 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00006 $0.04319
Opus 5 $0.00003 $0.02159
Sonnet 5 $0.00001 $0.00864
Haiku 4.5 $0.00001 $0.00432

Measured 2d ago against content hash d3ed6869c4a1, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 2d 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.

.agents/skills/api-design/SKILL.md · 621 lines

How it starts

The opening of the file, as written. The whole thing — 621 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

  1. RESTful Principles: Follow REST conventions
  2. Versioning: Version APIs from day one
  3. Documentation: APIs are only as good as their documentation
  4. Consistency: Consistent patterns across all endpoints
  5. Backward Compatibility: Don't break existing clients
  6. Architecture Alignment: API boundary decisions (resource decomposition, service splits, aggregate resources crossing domain boundaries) require /architect review and an ADR (see architect.md Phase 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 - Success
  • 201 Created - Resource created
  • 204 No Content - Success, no body
  • 400 Bad Request - Client error
  • 401 Unauthorized - Authentication required
  • 403 Forbidden - Authorization failed
  • 404 Not Found - Resource not found
  • 409 Conflict - Resource conflict
  • 422 Unprocessable Entity - Validation error
  • 500 Internal Server Error - Server error

URL Design:

  • Use nouns, not verbs: /users not /getUsers
  • Use plural nouns: /users not /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

Read the full file on GitHub · 621 lines

Changes

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.

  1. 2d ago First seen · 621 lines · 6 tokens per session scan A d3ed6869c4a1

Subscribe to this mod's changes

api-design is a skill published in the GitHub repository samibs/skillfoundry (12 stars, last pushed 1mo ago), licensed MIT. It adds 6 tokens to every session and 4,319 once invoked, about $0.0000 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-30.

Related

Other skills, from other repositories

memorix-troubleshooting

Use when Memorix MCP, setup, project binding, HTTP control plane, hooks, skills, or agent integration is missing, stale, or failing.

AVIDS2/memorix · 36 tokens

memorix-sessions

Use when resuming work, preparing handoff context, binding an HTTP control-plane project, or deciding whether sessionstart is useful.

AVIDS2/memorix · 31 tokens

ring:applying-composition-patterns

React composition patterns that scale. Avoid boolean prop proliferation by using compound components, lifting state, and composing internals. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or during architecture review. Skip for simple components with 1-2 props…

LerianStudio/ring · 68 tokens

ring:searching-code

Forensic code search and analysis with optional Chain of Draft (CoD) ultra-concise mode. Five-phase methodology (clarification, planning, execution, analysis, synthesis) with severity assessment. Use for targeted investigation of specific patterns, bugs, or vulnerabilities. Skip for broad architecture mapping (use…

LerianStudio/ring · 74 tokens

ring:exploring-codebases

Exploring a codebase across phases: scopes the target, detects architecture, components, and layers, deep-dives each discovered perspective, then synthesizes findings into actionable guidance with file:line evidence. Use to understand how a feature or system works before planning changes, or to orient on an unfamiliar…

LerianStudio/ring · 91 tokens

ring:auditing-dependency-security

Auditing a dependency for supply-chain risk before install (pip/npm/go/cargo): checks typosquatting, maintainer/age risk, vulnerability DBs (OSV, GHSA, Socket), and lockfile hash pinning, then emits a risk score and approve/conditional/escalate/block decision. Use when adding or updating a dependency, reviewing a…

LerianStudio/ring · 102 tokens