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-diataxisgit clone --depth 1 https://github.com/zircote-plugins/documentation-reviewWrote 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/commands/zircote-plugins/documentation-review/doc-diataxis)<a href="https://agentmods.dev/commands/zircote-plugins/documentation-review/doc-diataxis"><img src="https://agentmods.dev/badge/commands/zircote-plugins/documentation-review/doc-diataxis.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.00022 | $0.01060 |
| Opus 5 | $0.00011 | $0.00530 |
| Sonnet 5 | $0.00004 | $0.00212 |
| Haiku 4.5 | $0.00002 | $0.00106 |
Grade A, and why
doc-diataxis 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 3d 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analyze documentation against the Diátaxis framework.
Operation Mode
$IF($1, Mode: $1 $IF($2, Scope: @$2, Scope: all configured documentation paths), Ask the user which operation to perform:
- classify — Classify documents into Diátaxis quadrants (tutorial, how-to, reference, explanation)
- review — Review documents for Diátaxis quality criteria and mode purity
- gaps — Identify missing documentation across Diátaxis quadrants per feature/component
- audit — Full audit: classify + review + gaps in one pass )
Configuration Check
Use Glob tool to check if .claude/documentation-review.local.md exists.
If configuration exists, read it with Read tool and check for diataxis: section.
Use the following defaults if not configured:
strictness: standardrequire_frontmatter: truedoc_paths:from top-level plugin config, or require user to specify
Operations
Classify
For each documentation file in scope:
- Read the file content
- Check for
diataxis_typein frontmatter - If no frontmatter, apply the Diátaxis compass:
- Is the content action-oriented or cognition-oriented?
- Is it acquisition (learning) or application (working)?
- Assign the quadrant with confidence level (High/Medium/Low)
- Detect mode mixing — sections where the document shifts quadrant
- Report classification with recommendations
Review
For each documentation file in scope:
- Classify the document (if not already classified)
- Apply the quadrant-specific quality criteria from the
diataxisskill:- Tutorial: mode purity, learning path, reliability, tone, cross-references
- How-to: mode purity, goal clarity, practical focus, sequencing, cross-references
- Reference: mode purity, accuracy/completeness, structure, tone, cross-references
- Explanation: mode purity, depth/context, connections, scope discipline, cross-references
- Score each criterion using the weighted rubric
- Calculate aggregate Diátaxis score
- Flag mode mixing issues with specific locations
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.
- 3d ago First seen · 131 lines · 22 tokens per session scan A ad7aa054031f
doc-diataxis is a command published in the GitHub repository zircote-plugins/documentation-review (5 stars, last pushed 2mo ago), licensed MIT. It adds 22 tokens to every session and 1,060 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
capture-answer
Ingests an expert's answers to an L2 questionnaire in the abapwiki knowledge base: transforms the answers (filled in the interviews/ file or given verbally) into a canonical citable expert-answer (slices/ /inputs/expert-answers/), moves gaps to 'answered' and closes the questions. Use this skill when the owner/expert…
ingest-l1
L1 analysis loop for the abapwiki knowledge base: for each batch it launches the abap-analyzer sub-agent in parallel, then the adversarial judge abap-deepcheck (separate session), applies only the analyses that pass the fail-closed gate, and commits. Resumes exactly after an interruption. Use this skill to document…
research-l2
Executes Phases 1-3 of the L2 process of the abapwiki knowledge base on a slice: launches the abap-functional-researcher sub-agent (gap discovery + multi-source auto-research: wiki -> raw/docs -> MCP abap-fs on the system read-only -> standard knowledge), ingests gaps and evidence, and generates questionnaires for…
slice-init
Creates an L2 slice in the abapwiki knowledge base: a business process on which to build functional documentation. Writes the manifest (curated anchors + mandatory real owner) and derives the membership from the dependency graph (BFS hop<=2). Use this skill to start the L2 process on a custom domain. Does not promote…
ingest-l0
L0 bootstrap of the abapwiki knowledge base: creates stubs for all custom objects from the TADIR. Use this skill to initialize the repo from scratch or to ingest a new TADIR export. Deterministic operations (no LLM sub-agent), idempotent.
lint-audit
Checks the integrity of the abapwiki knowledge base: parseable YAML frontmatter, no broken wikilinks, resolvable [VERIFIED: path:N-M] citations, non-nested confidence tags, drift between wiki and DB, synchronization between canonical agent contracts and the .claude/agents/ copies. Use this skill periodically or after…