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 girijashankarj/cursor-handbook --skill api-docsgit clone --depth 1 https://github.com/girijashankarj/cursor-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/skills/girijashankarj/cursor-handbook/api-docs)<a href="https://agentmods.dev/skills/girijashankarj/cursor-handbook/api-docs"><img src="https://agentmods.dev/badge/skills/girijashankarj/cursor-handbook/api-docs/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/girijashankarj/cursor-handbook/api-docs"><img src="https://agentmods.dev/badge/skills/girijashankarj/cursor-handbook/api-docs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00021 | $0.00557 |
| Opus 5.5 | $0.00008 | $0.00223 |
| Sonnet 5.5 | $0.00004 | $0.00111 |
| Haiku 4.5 | $0.00002 | $0.00056 |
Grade A, and why
api-docs 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 1mo 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Create API Documentation
Trigger
When the user needs to document API endpoints.
Prerequisites
- API endpoints exist or are designed
- OpenAPI/Swagger tooling available (optional)
- Access to route definitions or handler files
Steps
Step 1: Inventory Endpoints
- List all API endpoints
- Group by resource/entity
- Note HTTP method and path for each
Step 2: Document Each Endpoint
For each endpoint:
- HTTP method and URL
- Description and purpose
- Authentication requirements
- Request parameters (path, query, header)
- Request body schema
- Response schemas (success + errors)
- Example request and response
- Rate limiting details
Step 3: Create OpenAPI Spec
- Define info, servers, security schemes
- Create component schemas (reusable)
- Define paths with all operations
- Add examples for all schemas
- Validate spec
Step 4: Generate Documentation
- Use Swagger UI or Redoc for interactive docs
- Host at
/api/docsor similar - Include in CI/CD for auto-updates
Step 5: Review
- All endpoints documented
- Examples are accurate and working
- Error responses documented
- Authentication flow documented
Completion Checklist
- All endpoints have method, URL, params, body, response
- Error responses (4xx, 5xx) documented
- Examples validated against live API or schema
- OpenAPI spec validates (if used)
If Step Fails
- Step 1 (inventory): Search for route definitions:
**/*.route*.ts,**/routes/**,app.get|post|put|delete - Step 3 (OpenAPI): Use minimal spec first; add complexity incrementally. Validate with
swagger-cli validate - Step 4 (generate): Swagger UI needs valid spec; Redoc is more forgiving. Check CORS if hosted separately
Example
Step 2 for POST /api/v1/orders: Method POST, URL /api/v1/orders, Body { customerId, items: [{ productId, quantity }] }, Response 201 { data: { id, status } }, Errors 400 validation, 404 customer not found.
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.
- 1mo ago First seen · 65 lines · 21 tokens per session scan A 6899e764e5f7
api-docs is a skill published in the GitHub repository girijashankarj/cursor-handbook (33 stars, last pushed 1mo ago), licensed MIT. It adds 21 tokens to every session and 557 once invoked, about $0.0001 per session on Opus 5.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
firebase-auth
Use when setting up auth, managing auth state, implementing email/password or social sign-in, handling auth errors, or managing users.
developing-genkit-dart
Use when building AI agents in Dart, implementing Genkit flows or tools, integrating LLMs into Dart or Flutter applications, or using Genkit Dart plugins.
firebase-cloud-functions
Use when calling callable functions (httpsCallable), passing data to server-side logic, handling function errors/timeouts, configuring regions, or testing with the Emulator Suite.
firebase-data-connect
Use when setting up Data Connect, writing GraphQL queries/mutations, configuring generated SDKs, handling offline, or applying security rules.
backend-pro-max
Backend & distributed-systems engineering intelligence — search 34 domain knowledge bases (languages, patterns, databases, messaging, cache, cloud, IaC, containers, observability, API design, auth, security, CI/CD, testing, architecture, scaling, consistency, performance, reliability, data, antipatterns, cost…
audit-backend-architecture
Read-only backend-architecture audit and pattern advisor, gated by stack. Use when "audit backend architecture", "which pattern should I use", "am I over-engineering", or "sync vs event-driven". Enforced boundaries → enhance-arch-boundaries.