Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/JansenAnalytics/claudexnpx agentmods add skills/jansenanalytics/claudex/doc-generatorWrote 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/jansenanalytics/claudex/doc-generator)<a href="https://agentmods.dev/skills/jansenanalytics/claudex/doc-generator"><img src="https://agentmods.dev/badge/skills/jansenanalytics/claudex/doc-generator/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/jansenanalytics/claudex/doc-generator"><img src="https://agentmods.dev/badge/skills/jansenanalytics/claudex/doc-generator.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00036 | $0.00540 |
| Opus 5.5 | $0.00014 | $0.00216 |
| Sonnet 5.5 | $0.00007 | $0.00108 |
| Haiku 4.5 | $0.00004 | $0.00054 |
Grade A, and why
doc-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 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
doc-generator
Auto-generate documentation from code: README files, JSDoc comments, API docs. Scans project structure, detects frameworks, and produces ready-to-use documentation.
When to Use
- Adding documentation to undocumented code
- Generating README from project structure
- Creating API documentation from Express/Fastify routes
- Adding JSDoc/TSDoc comments to JavaScript/TypeScript functions
- Keeping docs in sync with code changes
Scripts
generate-readme.sh
Auto-generate README.md by scanning project files.
# Generate README for current directory
bash scripts/generate-readme.sh --dir .
# Specify output file
bash scripts/generate-readme.sh --dir /path/to/project --output README.md
Detects: package.json, pyproject.toml, Makefile, Dockerfile, framework (React, Express, FastAPI, etc.)
Generates sections: Title, description, installation, usage, available scripts, project structure, dependencies, license.
jsdoc-gen.py
Generate JSDoc comments for undocumented JavaScript/TypeScript functions.
# Generate documented version
python3 scripts/jsdoc-gen.py --file src/utils.js --output src/utils.documented.js
# In-place modification
python3 scripts/jsdoc-gen.py --file src/utils.js --inplace
# Process all JS files in a directory
find src -name "*.js" -exec python3 scripts/jsdoc-gen.py --file {} --inplace \;
Analyzes: Parameter names, default values, TypeScript types, return statements, throw statements.
api-doc-gen.sh
Generate API documentation from Express/Fastify route files.
# Scan routes directory
bash scripts/api-doc-gen.sh --routes-dir src/routes/ --output API.md
# Single file
bash scripts/api-doc-gen.sh --routes-dir src/routes/users.js --output API.md
Extracts: HTTP method, path, middleware (auth, validation), handler name. Outputs Markdown with endpoint tables.
References
references/doc-templates.md— README templates, JSDoc patterns, Python docstring formatsreferences/doc-best-practices.md— What to document, keeping docs maintainable
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 · 74 lines · 36 tokens per session scan A 6e1ced3ed679
doc-generator is a skill published in the GitHub repository JansenAnalytics/claudex (5 stars, last pushed 3mo ago), licensed MIT. It adds 36 tokens to every session and 540 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
document-writer
Write or update technical documentation grounded in the real codebase. Use when the user asks for README, API docs, architecture guides, user guides, CONTRIBUTING docs, migration notes, or JSDoc/code comments, or wants technical docs rewritten into natural Chinese with correct terminology. Not for general prose…
documentation-writer
Write clear technical documentation including READMEs, API docs, architecture guides, and inline documentation. Use when creating or improving project documentation.
documentation-standards
Use when writing README files, API documentation, user guides, or technical documentation following industry standards from Google, Microsoft, and GitLab style guides.
doc-generator
Generate accurate, useful documentation for code — README files, API docs, inline docstrings, and changelogs. Use when user needs to document code, write a README, or generate API reference docs.
documentation-and-adrs
Use this skill when you need to record an architecture decision (ADR) or document the reasoning behind a design choice — when changing public APIs, shipping features that change behavior, or recording context that future engineers (human or agent) will need to understand the codebase. Does NOT replace code comments or…
documentation
Technical writing, API docs, and documentation best practices.