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 skills/ddr187/cursor-howto/doc-generatornpx skills add DDR187/cursor-howto --skill doc-generatorgit clone --depth 1 https://github.com/DDR187/cursor-howtoWrote 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/ddr187/cursor-howto/doc-generator)<a href="https://agentmods.dev/skills/ddr187/cursor-howto/doc-generator"><img src="https://agentmods.dev/badge/skills/ddr187/cursor-howto/doc-generator.svg" alt="Measured on agentmods" 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 | $0.00010 | $0.00503 |
| Opus 5 | $0.00005 | $0.00251 |
| Sonnet 5 | $0.00002 | $0.00101 |
| Haiku 4.5 | $0.00001 | $0.00050 |
Grade A, and why
Documentation Generator 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 4d 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Generator Skill
Overview
Automatically analyze code and generate documentation:
- API interface documentation
- Function/method documentation
- Type definition documentation
- Usage examples
Documentation Types
1. API Documentation
Auto-generated from API routes:
- Endpoint description
- Request parameters
- Response format
- Error codes
2. Function Documentation
Generated from code comments:
- Function description
- Parameter description
- Return value description
- Usage examples
3. Type Documentation
Generated from TypeScript types:
- Interface definitions
- Type descriptions
- Property descriptions
Output Format
# API Documentation
## {endpoint_name}
**Endpoint**: `{method} {path}`
### Description
{description}
### Request Parameters
| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| {param} | {type} | {required} | {description} |
### Request Example
```json
{
"{param}": "{value}"
}
Response Format
| Field | Type | Description |
|---|---|---|
| {field} | {type} | {description} |
Response Example
{
"{field}": "{value}"
}
Error Codes
| Status Code | Description |
|---|---|
| {code} | {description} |
---
## Usage Example
User: /docs src/api/users.ts
AI: Generating API documentation...
Users API Documentation
Get User List
Endpoint: GET /api/users
Description
Get a list of all users, supports pagination and filtering.
Request Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| page | number | No | Page number, default 1 |
| limit | number | No | Items per page, default 10 |
| search | string | No | Search keyword |
Response Format
| Field | Type | Description |
|---|---|---|
| data | User[] | User list |
| total | number | Total count |
| page | number | Current page number |
...
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.
- 4d ago First seen · 137 lines · 10 tokens per session scan A bdf530871582
Documentation Generator is a skill published in the GitHub repository DDR187/cursor-howto (2 stars, last pushed 5mo ago), licensed MIT. It adds 10 tokens to every session and 503 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…