generate-docs

A command for creating documentation from source code, such as API references, README files, and usage examples.

In plain words
What is it for?
Use it to document functions, parameters, return values, errors, examples, and project setup information.
Why use it?
It reduces the time spent manually keeping technical documentation in sync with the code.

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/cyperx84/claude-code-plugin-examples/generate-docs
Clone the repo
git clone --depth 1 https://github.com/cyperx84/claude-code-plugin-examples
Per session 5 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 639 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.00005 $0.00639
Opus 5 $0.00003 $0.00319
Sonnet 5 $0.00001 $0.00128
Haiku 4.5 $0.00001 $0.00064

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

Security

Grade A, and why

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

examples/04-real-world/docs-generator-plugin/commands/generate-docs.md · 130 lines

How it starts

The opening of the file, as written. The whole thing — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Generate Documentation

Generate docs for: $ARGUMENTS (or entire project)

Multi-Format Documentation

1. API Documentation

From code:

/**
 * Creates a new user account
 * @param userData - User registration data
 * @returns Created user with ID
 * @throws {ValidationError} If email invalid
 */
async function createUser(userData: UserData): Promise<User> {
  // Implementation
}

Generates:

## createUser

Creates a new user account.

### Parameters
- `userData` (UserData): User registration data
  - `email` (string, required): User's email address
  - `password` (string, required): User's password (min 8 chars)
  - `name` (string, optional): User's full name

### Returns
`Promise<User>` - Created user with assigned ID

### Throws
- `ValidationError` - If email format is invalid
- `DuplicateError` - If email already exists

### Example
```typescript
const user = await createUser({
  email: '[email protected]',
  password: 'SecurePass123',
  name: 'John Doe'
});
console.log(user.id); // '123e4567-e89b-12d3-a456-426614174000'

### 2. README Generation

Auto-generate README.md:
```markdown
# Project Name

[Auto-detected from package.json]

## Description
[From package.json description + code analysis]

## Features
- ✅ User authentication [detected from auth module]
- ✅ REST API [detected from routes]
- ✅ Database integration [detected from ORM usage]

## Installation
[From package.json scripts + dependencies]

## Usage
[From main entry points + examples in tests]

## API Reference
[Generated from code]

## Contributing
[Template]

## License
[From package.json]

3. Database Schema Docs

# Database Schema

## users Table

| Column | Type | Constraints | Description |
|--------|------|-------------|-------------|
| id | UUID | PRIMARY KEY | Unique user identifier |
| email | VARCHAR(255) | UNIQUE, NOT NULL | User's email |
| created_at | TIMESTAMP | DEFAULT NOW() | Account creation |

### Relationships
- **Has Many** orders (via user_id)
- **Has One** profile (via user_id)

### Indexes
- `idx_users_email` (email) - For login queries

Read the full file on GitHub · 130 lines

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 · 130 lines · 5 tokens per session scan A 9d889b8d0c0a

Subscribe to this mod's changes

generate-docs is a command published in the GitHub repository cyperx84/claude-code-plugin-examples (2 stars, last pushed 10mo ago), licensed MIT. It adds 5 tokens to every session and 639 once invoked, about $0.0000 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.