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 rules/d-padmanabhan/agent-engineering-handbook/320-api-designgit clone --depth 1 https://github.com/d-padmanabhan/agent-engineering-handbookWrote 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/rules/d-padmanabhan/agent-engineering-handbook/320-api-design)<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>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.00020 | $0.10236 |
| Opus 5 | $0.00010 | $0.05118 |
| Sonnet 5 | $0.00004 | $0.02047 |
| Haiku 4.5 | $0.00002 | $0.01024 |
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 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) andskills/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(),
},
});
});
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.
- 3d ago First seen · 1,845 lines · 20 tokens per session scan A 08c1ac96a381
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.
Other cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.