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/oakensoul/nextjs-cursor-prompts/documentation-create-apigit clone --depth 1 https://github.com/oakensoul/nextjs-cursor-promptsWhat 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.00000 | $0.06642 |
| Opus 5 | $0.00000 | $0.03321 |
| Sonnet 5 | $0.00000 | $0.01328 |
| Haiku 4.5 | $0.00000 | $0.00664 |
Grade A, and why
documentation-create-api 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
const apiClient = axios.create({ How it starts
The opening of the file, as written. The whole thing — 1,050 lines — stays where its author put it; the contents beside it link to each section on GitHub.
API Documentation Creation and Generation
This prompt generates comprehensive API documentation including endpoint specifications, authentication flows, integration examples, and developer guides with proper OpenAPI standards.
🎯 API DOCUMENTATION OBJECTIVES:
- ANALYZE existing API structure and extract complete endpoint specifications
- GENERATE OpenAPI 3.0 specification with comprehensive schemas and examples
- CREATE integration guides with practical code examples in multiple languages
- DOCUMENT authentication flows with security considerations and examples
- ESTABLISH maintenance processes for keeping documentation current with code changes
🔍 API DISCOVERY AND ANALYSIS:
STEP 1: API Endpoint Discovery
Automated Endpoint Detection:
# Discover API endpoints across the codebase
echo "🔍 Discovering API endpoints..."
# Next.js API routes discovery
if [ -d "src/app/api" ] || [ -d "app/api" ] || [ -d "pages/api" ]; then
echo "## Next.js API Routes:"
find . -path "*/api/*" -name "*.ts" -o -name "*.js" | grep -E "(route|api)" | sort
fi
# Express.js routes discovery
echo -e "\n## Express/Node.js Routes:"
grep -r "app\.\(get\|post\|put\|delete\|patch\)" --include="*.ts" --include="*.js" src/ 2>/dev/null | head -20
# FastAPI/Python routes (if applicable)
echo -e "\n## Python API Routes:"
grep -r "@app\.\(get\|post\|put\|delete\|patch\)" --include="*.py" . 2>/dev/null | head -10
# GraphQL schema discovery
echo -e "\n## GraphQL Schema:"
find . -name "*.graphql" -o -name "schema.ts" -o -name "typeDefs.ts" | head -10
# API middleware and authentication
echo -e "\n## Authentication Middleware:"
grep -r "auth\|jwt\|token" --include="*.ts" --include="*.js" src/ | grep -E "(middleware|auth)" | head -10
API Structure Analysis:
# Analyze API structure and patterns
echo "📊 Analyzing API structure..."
# Check for OpenAPI/Swagger existing docs
echo "## Existing API Documentation:"
find . -name "swagger*" -o -name "openapi*" -o -name "api-docs*" | head -10
# Analyze request/response patterns
echo -e "\n## Request/Response Patterns:"
grep -r "Request\|Response" --include="*.ts" src/ | grep -E "(interface|type)" | head -10
# Database models (for API data structures)
echo -e "\n## Data Models:"
find . -name "*.model.ts" -o -name "*.schema.ts" -o -name "prisma.schema" | head -10
# API versioning strategy
echo -e "\n## API Versioning:"
grep -r "v1\|v2\|version" --include="*.ts" --include="*.js" src/ | grep -i api | head -5
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.
- 2d ago First seen · 1,050 lines · 0 tokens per session scan A d1cdc6cf974d
documentation-create-api is a cursor rule published in the GitHub repository oakensoul/nextjs-cursor-prompts (4 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 6,642 tokens. 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-31.
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.