Borrowing it
Nothing to install: this file belongs to fwornle/coding. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/fwornle/coding/main/.claude/commands/documentation-style.mdgit clone --depth 1 https://github.com/fwornle/codingWrote 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/fwornle/coding/documentation-style)<a href="https://agentmods.dev/commands/fwornle/coding/documentation-style"><img src="https://agentmods.dev/badge/commands/fwornle/coding/documentation-style/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/commands/fwornle/coding/documentation-style"><img src="https://agentmods.dev/badge/commands/fwornle/coding/documentation-style.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.00073 | $0.01787 |
| Opus 5.5 | $0.00029 | $0.00715 |
| Sonnet 5.5 | $0.00015 | $0.00357 |
| Haiku 4.5 | $0.00007 | $0.00179 |
Grade A, and why
documentation-style 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 — 232 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Style Guide
Enforce consistent styling for documentation artifacts (PlantUML, Mermaid, markdown, PNG diagrams).
Instructions
When creating or modifying documentation artifacts, follow these guidelines strictly.
HARD RULES — File Placement (Constraint-Monitored)
These rules are enforced by the constraint monitor. Violations trigger system health degradation.
| Artifact | MUST be placed in | NEVER place in |
|---|---|---|
.puml files |
docs/puml/ |
Root, src/, temp dirs, or anywhere else |
Generated .png |
docs/images/ |
Same dir as .puml, root, or temp dirs |
| Image references in markdown |  |
 or absolute paths |
When using tools that generate diagrams (e.g., semantic-analysis_generate_plantuml_diagrams, create_insight_report):
- Always specify output paths pointing to
docs/puml/for.pumlfiles - Always specify
docs/images/for rendered PNG output - Use the
nameparameter as kebab-case without path — the tool writes to CWD, so run fromdocs/puml/or move files after generation - If a tool does NOT support specifying output directory, move the generated files immediately after creation
semantic-analysis_generate_plantuml_diagrams specific workflow:
- Call the tool with
nameset to a kebab-case descriptor (e.g.,"constraint-monitor-architecture") - After generation, immediately move output:
mv *.puml docs/puml/ && mv *.png docs/images/ - Verify the generated
.pumlcontains!include _standard-style.puml— add it if missing - Update any markdown references to point to
docs/images/
semantic-analysis_create_insight_report specific workflow:
- Insight reports with diagrams write to
.sa/insights/by default — this is fine for internal analysis - If diagrams from insights need to be committed to docs, copy them to
docs/puml/anddocs/images/
PlantUML file naming — MUST use component-purpose.puml kebab-case convention:
constraint-monitor-architecture.puml✓ConstraintMonitorArchitecture.puml✗diagram-v2.puml✗ (incremental naming forbidden)
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 Changed · +5 lines · +73 tokens per session c2bdb81591a3
- 1mo ago First seen · 227 lines · 0 tokens per session scan A a5b4bb22a8d4
documentation-style is a command published in the GitHub repository fwornle/coding (2 stars, last pushed today), licensed MIT. It adds 73 tokens to every session and 1,787 once invoked, about $0.0003 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-08-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.