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 autohandai/community-skills --skill api-design-restfulgit clone --depth 1 https://github.com/autohandai/community-skillsWrote 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/autohandai/community-skills/api-design-restful)<a href="https://agentmods.dev/skills/autohandai/community-skills/api-design-restful"><img src="https://agentmods.dev/badge/skills/autohandai/community-skills/api-design-restful/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/autohandai/community-skills/api-design-restful"><img src="https://agentmods.dev/badge/skills/autohandai/community-skills/api-design-restful.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.00016 | $0.01436 |
| Opus 5 | $0.00008 | $0.00718 |
| Sonnet 5 | $0.00003 | $0.00287 |
| Haiku 4.5 | $0.00002 | $0.00144 |
Grade A, and why
api-design-restful 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 9d 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 — 237 lines — stays where its author put it; the contents beside it link to each section on GitHub.
RESTful API Design
Core Principles
- Resource-Oriented - URLs represent nouns, not verbs
- Stateless - Each request contains all necessary information
- Consistent - Use standard HTTP methods and status codes
- Versioned - Support API evolution without breaking clients
URL Structure
# Collection resources
GET /api/v1/users # List users
POST /api/v1/users # Create user
# Individual resources
GET /api/v1/users/:id # Get user
PUT /api/v1/users/:id # Replace user
PATCH /api/v1/users/:id # Update user
DELETE /api/v1/users/:id # Delete user
# Nested resources
GET /api/v1/users/:id/posts # User's posts
POST /api/v1/users/:id/posts # Create post for user
# Filtering, sorting, pagination
GET /api/v1/users?status=active&sort=-createdAt&page=2&limit=20
Response Structure
Success Response
interface SuccessResponse<T> {
success: true;
data: T;
meta?: {
page?: number;
limit?: number;
total?: number;
totalPages?: number;
};
}
// Example
{
"success": true,
"data": { "id": "123", "name": "John" },
"meta": { "requestId": "abc-123" }
}
Error Response
interface ErrorResponse {
success: false;
error: {
code: string; // Machine-readable code
message: string; // Human-readable message
details?: unknown; // Field-level errors
};
}
// Example
{
"success": false,
"error": {
"code": "VALIDATION_ERROR",
"message": "Invalid request body",
"details": {
"email": "Invalid email format",
"age": "Must be a positive number"
}
}
}
HTTP Status Codes
// Success
200 OK // Successful GET, PUT, PATCH
201 Created // Successful POST
204 No Content // Successful DELETE
// Client Errors
400 Bad Request // Validation errors
401 Unauthorized // Missing/invalid auth
403 Forbidden // Insufficient permissions
404 Not Found // Resource doesn't exist
409 Conflict // Duplicate/state conflict
422 Unprocessable // Semantic errors
429 Too Many Reqs // Rate limited
// Server Errors
500 Internal Error // Unexpected server error
503 Unavailable // Service temporarily down
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.
- 9d ago First seen · 237 lines · 16 tokens per session scan A 3e8d19dd8100
api-design-restful is a skill published in the GitHub repository autohandai/community-skills (11 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 16 tokens to every session and 1,436 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
amazon-location-service
Integrates Amazon Location Service APIs for AWS applications. Use this skill when users want to add maps (interactive MapLibre or static images); geocode addresses to coordinates or reverse geocode coordinates to addresses; calculate routes, travel times, or service areas; find places and businesses through text…
amplify-workflow
Build and deploy full-stack web and mobile apps with AWS Amplify Gen2 (TypeScript code-first). Covers auth (Cognito), data (AppSync/DynamoDB including schema modeling, enum types, relationships, authorization rules), storage (S3), functions, APIs, and AI (Amplify AI Kit with Bedrock). Supports React, Next.js, Vue…
aws-lambda-durable-functions
Build resilient, long-running, multi-step applications with AWS Lambda durable functions with automatic state persistence, retry logic, and orchestration for long-running executions. Covers the critical replay model, step operations, wait/callback patterns, error handling with saga pattern, testing with…
api-gateway
Build, manage, and operate APIs with Amazon API Gateway (REST, HTTP, and WebSocket). Triggers on phrases like: API Gateway, REST API, HTTP API, WebSocket API, custom domain, Lambda authorizer, usage plan, throttling, CORS, VPC link, private API. Also covers troubleshooting API Gateway errors (4xx, 5xx, timeout, CORS…
aws-lambda
Design, build, deploy, test, and debug serverless applications with AWS Lambda. Triggers on phrases like: Lambda function, event source, serverless application, API Gateway, EventBridge, Step Functions, serverless API, event-driven architecture, Lambda trigger. For deploying non-serverless apps to AWS, use…
agentsop-http-tool-wrapping
Decision protocol for wrapping a REST / GraphQL / RPC API as a tool an LLM agent can call. The load-bearing premise: the tool surface is an LM-friendly subset of the API surface — one tool per user intent, not one per endpoint. Activates when a coder agent must expose an external HTTP API to a model (function calling…