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 skills add The-Artificer-of-Ciphers-LLC/skills-from-the-artificer --skill writing-docs-with-diataxisgit clone --depth 1 https://github.com/The-Artificer-of-Ciphers-LLC/skills-from-the-artificerWrote 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/the-artificer-of-ciphers-llc/skills-from-the-artificer/writing-docs-with-diataxis)<a href="https://agentmods.dev/skills/the-artificer-of-ciphers-llc/skills-from-the-artificer/writing-docs-with-diataxis"><img src="https://agentmods.dev/badge/skills/the-artificer-of-ciphers-llc/skills-from-the-artificer/writing-docs-with-diataxis/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/the-artificer-of-ciphers-llc/skills-from-the-artificer/writing-docs-with-diataxis"><img src="https://agentmods.dev/badge/skills/the-artificer-of-ciphers-llc/skills-from-the-artificer/writing-docs-with-diataxis.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.00126 | $0.02016 |
| Opus 5.5 | $0.00050 | $0.00806 |
| Sonnet 5.5 | $0.00025 | $0.00403 |
| Haiku 4.5 | $0.00013 | $0.00202 |
Grade A, and why
writing-docs-with-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 9d 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
writing-docs-with-diataxis
Every section below ends with Source: tags. Keys resolve to diataxis.fr pages in the list at the bottom; evidence.md says how strong each source is. Anything tagged [repo judgment] is not Diátaxis and must not be presented as such.
Diátaxis (Daniele Procida) solves problems of documentation content (what to write), style (how to write it) and architecture (how to organise it). It identifies four distinct user needs and four corresponding forms of documentation, and "crossing or blurring the boundaries ... is at the heart of a vast number of problems in documentation." Most doc problems are two needs smeared onto one page. Source: [Home] [Start] [Map] [Colophon]
1. The compass: classify before you write or edit
Ask two questions of the content (or of what the reader needs):
- Action or cognition? Does it inform what the user does (practical steps) or what they know (theoretical, propositional knowledge)?
- Acquisition or application? Is the user at study or at work?
| If the content... | ...and serves the user's... | ...it is |
|---|---|---|
| informs action | acquisition of skill | a tutorial (a lesson; learning-oriented) |
| informs action | application of skill | a how-to guide (a recipe; goal-oriented) |
| informs cognition | application of skill | reference (a description; information-oriented) |
| informs cognition | acquisition of skill | explanation (a discussion; understanding-oriented) |
Quick test by the question the reader is asking: tutorial "Can you teach me to...?", how-to "How do I...?", reference "What is...?", explanation "Why...?". Use the compass terms flexibly while finding bearings; apply it to a whole page or to a single sentence. Run it when you feel doubt, because "sometimes intuition provides an immediate answer that is also wrong." Source: [Compass] [Map] [Start]
2. Write to the type (one-screen version)
Full principles, language patterns and checklists are in references/types.md; read the section for the type you are writing.
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 86 lines · 126 tokens per session scan A 4eda959fb920
writing-docs-with-diataxis is a skill published in the GitHub repository The-Artificer-of-Ciphers-LLC/skills-from-the-artificer (6 stars, last pushed yesterday), licensed MIT. It adds 126 tokens to every session and 2,016 once invoked, about $0.0005 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-10-18.
Other skills, from other repositories
offensive-vuln-classes
Exploit development curriculum covering core vulnerability classes with real-world CVE case studies: stack/heap buffer overflows, use-after-free, integer overflows, format strings, type confusion, and race conditions. Use when learning or teaching vuln classes, researching specific CVE patterns, or building exploit…
explorer-interface-brief
Use when asked to design the interface for an interactive 3D explorer, plan a UI for exploring a 3D model of a topic, or write an image-model prompt for a 3D learning app mock-up. Produces, from a topic, the UI design brief (audience, layout, panels, interactions, label style, colour palette, accessibility) and an…
model-prompt-pack
Use when asked to write prompts for image-to-3D or text-to-3D tools, generate 3D models of a topic's parts, plan the assets for a 3D explorer, or build a labelled parts list with sources. Produces prompts for image-to-3D tools, one per object, plus a parts list for labelling in which every label names a trusted…
explorer-pipeline
Use when asked to make an interactive 3D explorer of a topic from start to finish, go from a topic to a clickable 3D learning page, or run the whole 3D explorer process. Produces a staged run of explorer-interface-brief, model-prompt-pack and explorer-viewer-builder in order for one topic, with the hand-offs between…
spot-ai-mistakes
Learn to recognize where and how AI tends to go wrong — the specific failure patterns — so you catch its mistakes on sight instead of getting burned by confident errors. Use when asked how do I know when AI is wrong, what are AI's common mistakes, how do I catch AI errors, or where does AI mess up. Produces the…
financial-statement-explainer
Explain a financial statement (P&L, balance sheet, or cash flow) in plain English. Use when asked to explain a P&L / income statement, a balance sheet, a cash flow statement, or to make financials understandable to a non-finance reader. Produces a plain-language walkthrough — what each section means, the line items…