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 commands/zircote-plugins/documentation-review/doc-creategit clone --depth 1 https://github.com/zircote-plugins/documentation-reviewWhat 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.01004 |
| Opus 5 | $0.00005 | $0.00502 |
| Sonnet 5 | $0.00002 | $0.00201 |
| Haiku 4.5 | $0.00001 | $0.00100 |
Grade A, and why
doc-create 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 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.
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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate new documentation based on codebase analysis.
Documentation Type
$IF($1, Generate: $1 documentation, Ask the user which type of documentation to create:
- readme: Generate README.md from project analysis
- api: Generate API documentation from code/specs
- template: Create documentation from standard templates )
Diátaxis Quadrant Selection (enabled by default; disable with diataxis.enabled: false)
Before generating content, determine the Diátaxis quadrant:
-
Check if the documentation type maps to a quadrant:
- readme → typically mixed (overview), flag for later splitting
- api → Reference quadrant
- template → depends on template type
-
Ask the user which quadrant the document serves:
- Tutorial: learning-oriented, guided experience
- How-to: task-oriented, solve a specific problem
- Reference: information-oriented, technical descriptions
- Explanation: understanding-oriented, context and background
-
Apply the quadrant's structure template from the
diataxisskill -
Set
diataxis_typein frontmatter of the generated document -
Use the quadrant's tone and style guidelines during generation
Generation Workflows
README Generation (type: readme)
-
Analyze Project Structure
- Find package.json, pyproject.toml, go.mod, Cargo.toml
- Identify primary language and framework
- List main source directories
-
Extract Project Information
- Project name and description from manifest
- Dependencies and their purposes
- Available scripts/commands
- Entry points and exports
-
Generate Sections
- Title and description
- Features (from code analysis)
- Installation (from package manager)
- Quick start (from examples or main entry)
- Configuration (from config files)
- API overview (from exports)
- Contributing (standard template)
- License
-
Write README.md Use Write tool to create the file.
API Documentation (type: api)
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 · 161 lines · 10 tokens per session scan A a689094e9431
doc-create is a command published in the GitHub repository zircote-plugins/documentation-review (5 stars, last pushed 2mo ago), licensed MIT. It adds 10 tokens to every session and 1,004 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 commands, from other repositories
wiki-retro
Save an atomic insight from the current task into the wiki. Creates a single markdown file that layered recall surfaces in future sessions.
doc
Use this command to create a new feature doc, how-to, concept, reference, or troubleshooting guide — it scaffolds the file, frontmatter, structure, and sidebar entry.
graph
Extract prerequisite concept graph from converted course materials and write course-index/concept-graph.md.
reindex
Idempotent reindex of an existing course — rewrite retired coverage.md tier markers to canonical vocabulary and materialize errors/log.md nature/phase into the on-disk schema (header keys == data keys), in place and atomically, WITHOUT running analyze.
publish
Publishes the portfolio: runs the link check, hands off to the content editor for any last fixes, then follows the deploy runbook.
alt
Import an Exam Radar (OPTIMETA Alt plugin) export and fold its lecture-emphasis exam signal into the course index — radar.md, a lecture-emphasis column on coverage.md, and a gold-zone weakmap.