320-api-design

320-api-design is a cursor rule for coding agents from d-padmanabhan/agent-engineering-handbook. It costs 20 tokens per session (10,236 once invoked), scanned A, original, MIT.

A set of guidelines for designing REST, GraphQL, and gRPC APIs—the interfaces that let software systems communicate. It covers endpoint behavior, security, versioning, schemas, and documentation.

In plain words
What is it for?
Use it when designing or reviewing API endpoints, choosing authentication and authorization rules, planning versions, defining schemas, or writing API documentation.
Why use it?
It helps teams make APIs consistent and easier to use, while avoiding compatibility, security, and documentation problems as the API changes.

Cursor rule

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 rules/d-padmanabhan/agent-engineering-handbook/320-api-design
Clone the repo
git clone --depth 1 https://github.com/d-padmanabhan/agent-engineering-handbook

Wrote 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.

agentmods badge for 320-api-design

README.md
[![agentmods](https://agentmods.dev/badge/rules/d-padmanabhan/agent-engineering-handbook/320-api-design.svg)](https://agentmods.dev/rules/d-padmanabhan/agent-engineering-handbook/320-api-design)
Your own site
<a href="https://agentmods.dev/rules/d-padmanabhan/agent-engineering-handbook/320-api-design"><img src="https://agentmods.dev/badge/rules/d-padmanabhan/agent-engineering-handbook/320-api-design.svg" alt="Measured on agentmods" height="20"></a>
Per session 20 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 10,236 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. 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.00020 $0.10236
Opus 5 $0.00010 $0.05118
Sonnet 5 $0.00004 $0.02047
Haiku 4.5 $0.00002 $0.01024

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

Security

Grade A, and why

320-api-design scanned grade A with 1 finding 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -I https://api.acme.com/api/v1/users
rules/320-api-design.mdc · 1,845 lines

How it starts

The opening of the file, as written. The whole thing — 1,845 lines — stays where its author put it; the contents beside it link to each section on GitHub.

API Design Best Practices

Audience: engineers designing and reviewing REST, GraphQL, and gRPC APIs Goal: Create consistent, secure, well-documented APIs that provide excellent developer experience

[!NOTE] This rule covers the API surface (verbs, status codes, versioning, authn/authz, schemas). For the transport and wire format layer beneath it - TCP keepalive, HoL blocking, TTFB budget, HTTP/1.1 vs 2 vs 3, gRPC/Protobuf vs REST/JSON decision matrix, connection pooling, long-lived connections - see 325-networking.mdc (file-scoped non-negotiables) and skills/networking-transport/ (the depth). The two layers compose; both are required for production API decisions.

API Design Philosophy (Core Principles)

Core Principles:

  • "Consistency is king" - Follow conventions consistently across all endpoints
  • "Developer experience matters" - APIs should be intuitive, well-documented, and easy to use
  • "Versioning from day one" - Plan for evolution, maintain backward compatibility
  • "Security by default" - Authentication, authorization, rate limiting, input validation
  • "Documentation is part of the API" - Clear, accurate, up-to-date docs are essential
  • "Fail fast, fail clearly" - Return meaningful error messages with actionable information
  • "Performance matters" - Use pagination, caching, compression where appropriate
  • "Idempotency where possible" - Make operations safe to retry

Applying API Design Principles:

// BAD: Inconsistent, insecure, undocumented
app.get('/getUsers', (req, res) => {
  const users = db.getUsers();
  res.json(users);
});

// GOOD: Consistent, secure, documented
/**
 * GET /api/v1/users
 * List users with pagination
 *
 * @query limit - Number of results (default: 20, max: 100)
 * @query offset - Pagination offset (default: 0)
 * @returns {User[]} Array of users
 */
app.get('/api/v1/users', authenticate, authorize('read:users'), async (req, res) => {
  const { limit = 20, offset = 0 } = req.query;

  // Validate input
  const validatedLimit = Math.min(parseInt(limit) || 20, 100);
  const validatedOffset = Math.max(parseInt(offset) || 0, 0);

  const users = await userService.listUsers({
    limit: validatedLimit,
    offset: validatedOffset,
  });

  res.json({
    data: users,
    pagination: {
      limit: validatedLimit,
      offset: validatedOffset,
      total: await userService.countUsers(),
    },
  });
});

Read the full file on GitHub · 1,845 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. 3d ago First seen · 1,845 lines · 20 tokens per session scan A 08c1ac96a381

Subscribe to this mod's changes

320-api-design is a cursor rule published in the GitHub repository d-padmanabhan/agent-engineering-handbook (16 stars, last pushed 4d ago), licensed MIT. It adds 20 tokens to every session and 10,236 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.