api-docs

A command that examines a codebase's web API and creates an OpenAPI description, written endpoint documentation, and a Postman collection. An API is the interface that lets software exchange requests and data.

In plain words
What is it for?
Use it to document routes, parameters, request and response data, authentication, middleware, errors, examples, and collections for testing API calls.
Why use it?
It turns route definitions and code types into reference material, reducing the need to document every endpoint by hand.

Command

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 commands/alphaaiservice/cortex/api-docs
Clone the repo
git clone --depth 1 https://github.com/alphaaiservice/cortex
Per session 22 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 440 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. 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.00022 $0.00440
Opus 5 $0.00011 $0.00220
Sonnet 5 $0.00004 $0.00088
Haiku 4.5 $0.00002 $0.00044

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

Security

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

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.

commands/api-docs.md · 84 lines

What it actually says

API Documentation Generator

Generate comprehensive API documentation for this project.

Step 1: Discover API Endpoints

Scan for route definitions:

  • Express/Fastify: router.get/post/put/delete, app.get/post
  • FastAPI: @app.get/post, @router.get/post
  • Django: urlpatterns, @api_view
  • NestJS: @Get/@Post/@Put/@Delete
  • Spring: @GetMapping/@PostMapping

For each endpoint, extract:

  • HTTP method and path
  • Request parameters (path, query, body)
  • Request/response types
  • Authentication requirements
  • Middleware applied
  • Error responses

Step 2: Generate OpenAPI Spec

Create docs/openapi.yaml with:

  • API info and server URLs
  • Authentication schemes
  • All endpoints with full schemas
  • Request/response examples
  • Error response schemas

Step 3: Generate Markdown Docs

Create docs/API.md:

# API Documentation

## Authentication
[Auth mechanism description]

## Endpoints

### [Group Name]

#### `METHOD /path`
**Description**: [what it does]

**Parameters**:
| Name | In | Type | Required | Description |
|------|------|------|----------|-------------|

**Request Body**:
```json
{ "example": "body" }

Response (200):

{ "example": "response" }

Errors:

Code Description

## Step 4: Generate Postman Collection

Create `docs/postman_collection.json` with:
- All endpoints organized by group
- Pre-configured request bodies
- Environment variable placeholders
- Example responses

## Output

1. `docs/openapi.yaml` — OpenAPI 3.0 specification
2. `docs/API.md` — Human-readable API docs
3. `docs/postman_collection.json` — Importable Postman collection
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. yesterday First seen · 84 lines · 22 tokens per session scan A c6235fcd0ddf

Subscribe to this mod's changes

api-docs is a command published in the GitHub repository alphaaiservice/cortex (1 stars, last pushed 25d ago), licensed MIT. It adds 22 tokens to every session and 440 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-08-31.