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 Cratis/AI --skill cratis-documentation-writinggit clone --depth 1 https://github.com/Cratis/AIWrote 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/cratis/ai/cratis-documentation-writing)<a href="https://agentmods.dev/skills/cratis/ai/cratis-documentation-writing"><img src="https://agentmods.dev/badge/skills/cratis/ai/cratis-documentation-writing/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/cratis/ai/cratis-documentation-writing"><img src="https://agentmods.dev/badge/skills/cratis/ai/cratis-documentation-writing.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.00080 | $0.02710 |
| Opus 5.5 | $0.00032 | $0.01084 |
| Sonnet 5.5 | $0.00016 | $0.00542 |
| Haiku 4.5 | $0.00008 | $0.00271 |
Grade A, and why
cratis-documentation-writing 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 13d 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 — 221 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation writing
A developer arrives with a job to do, not with an interest in our repository structure. Start from that job: what did they try, what stopped them, and what would let them know they succeeded? Use Diátaxis as a compass for each page's primary purpose, not a purity test. This skill governs content and reader journeys; the owning repository governs page placement, navigation, and rendering.
Classify before writing
Determine which quadrant the page belongs to before drafting:
| Type | Orientation | Analogy | When to use |
|---|---|---|---|
| Tutorial | Learning | A lesson | Guide a newcomer step-by-step to a successful first outcome |
| How-to guide | Problem-solving | A recipe | Show an experienced user how to accomplish a specific task |
| Reference | Information | A dictionary | Describe the technical machinery — APIs, attributes, configuration |
| Explanation | Understanding | A discussion | Clarify why something works the way it does, trade-offs, architecture |
Rules per type:
- Tutorial — lead a newcomer through one realistic, threaded outcome. Each step has a visible result. Briefly explain the invisible effect of a step, then link to an explanation for deeper theory; do not interrupt the lesson with a reference dump. Show the smallest safe configuration that runs before presenting options: bind local services to loopback, label development credentials as such, and put host and configuration alternatives in linked how-to guides. Make the first snippet the convention path, with no registration or wiring a convention already does, then name what the framework did that the reader cannot see.
- How-to guide — assume competence. State the goal, list prerequisites, give the steps, done. No teaching.
- Reference — exhaustive within its declared scope and terse. For each public option or API, cover type, required/optional status, default, valid values, return behavior, errors and compatibility where applicable. State scope and link to a working usage example; do not turn it into a lesson.
- Explanation — no steps. Discuss concepts, trade-offs, and design decisions. Diagrams are welcome here.
What ships with it
3 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.
- 13d ago Changed · +5 lines 0d925576bace
- 17d ago Changed · +15 lines 2a962325535f
- 23d ago Changed · +35 lines · +1 tokens per session c87621eff6b7
- 24d ago Changed · +44 lines · -10 tokens per session 953b2de9ceab
- 1mo ago First seen · 122 lines · 89 tokens per session scan A 85d63c6a632a
cratis-documentation-writing is a skill published in the GitHub repository Cratis/AI (4 stars, last pushed today), licensed MIT. It adds 80 tokens to every session and 2,710 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-09-11.
Other skills, from other repositories
event-driven-architecture
Event-driven architecture patterns with event sourcing, CQRS, and message-driven communication. Use when designing distributed systems, microservices communication, or systems requiring eventual consistency and scalability.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…