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-engineering-docs-authoringgit 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-engineering-docs-authoring)<a href="https://agentmods.dev/skills/cratis/ai/cratis-engineering-docs-authoring"><img src="https://agentmods.dev/badge/skills/cratis/ai/cratis-engineering-docs-authoring.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.1 | $0.00061 | $0.00778 |
| Opus 5 | $0.00030 | $0.00389 |
| Sonnet 5 | $0.00012 | $0.00156 |
| Haiku 4.5 | $0.00006 | $0.00078 |
Grade A, and why
cratis-engineering-docs-authoring 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cratis documentation authoring
Draft one accurate Cratis documentation page in the voice and structure required by its document type. This skill owns content. It does not decide which repository owns a page, wire site navigation, locate an existing source page, or perform visual QA.
Required inputs
Before drafting, establish:
- the owning repository and destination page;
- document type: tutorial, how-to, explanation, or reference;
- target reader and the outcome they need;
- authoritative product source for every API, command, version, and capability;
- explicit scope and important exclusions.
Use repository evidence to resolve routine details. Ask only when materially different document types, audiences, or product choices remain plausible.
Route near misses
- New-page placement or navigation is unresolved: defer to
cratis-engineering-docs-add-page. - The request changes an existing page whose source location is unresolved:
defer to
cratis-engineering-docs-edit-page. - The request is to render, screenshot, or diagnose visual layout: defer to
cratis-engineering-docs-visual-qa. - A product/API claim lacks first-party source evidence: stop and identify the missing authority instead of drafting the claim.
- The subject is not Cratis product or engineering documentation: do not apply this skill.
Write one document type
Do not mix Diátaxis types on one page:
| Type | Reader need | Shape |
|---|---|---|
| Tutorial | Learn by completing a guided outcome | Ordered steps with visible results |
| How-to | Solve one concrete problem | Prerequisites, direct procedure, completion check |
| Explanation | Understand why and when | Concepts, boundaries, trade-offs, diagram |
| Reference | Look up exact information | Exhaustive tables, fields, commands, signatures |
For the detailed mechanical format, read site-format.md.
Drafting workflow
- Open with the reader's concrete friction and the Cratis capability that relieves it.
- Organize by the reader's workflow, not by implementation namespaces or an alphabetical API dump.
- Use active voice, present tense, second person, and American English.
- Explain the invisible behavior after each example: what the framework does and why the boundary matters.
- Verify every API and command against first-party source at the applicable revision. Never translate a C# example into another client language by guess.
- State maturity, authorization, side effects, unsupported surfaces, and when a simpler approach is better.
- Show a visible result in tutorials and procedures. Use Mermaid for a non-trivial explanation.
- End with the natural next page or workflow.
What ships with it
2 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.
- 3d ago First seen · 87 lines · 61 tokens per session scan A 014f2e7b55d4
cratis-engineering-docs-authoring is a skill published in the GitHub repository Cratis/AI (2 stars, last pushed today), licensed MIT. It adds 61 tokens to every session and 778 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
build-sample-matrix
Build the matrix of all the samples throughout different frameworks.
architecture-paradigm-cqrs-es
Applies CQRS and Event Sourcing for read/write separation and audit trails. Use when designing systems with complex domain logic or full state-change history.
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.
cqrs-event-sourcing
CQRS and Event Sourcing patterns for scalable, auditable systems with separated read/write models. Use when building audit-required systems, implementing temporal queries, or designing high-scale applications with complex domain logic.
dotnet-mentor-en
Adaptive text-first C# and .NET mentor from the first program to junior backend developer skills. Use for learning intent: starting or continuing a structured course, explaining C#/.NET in plain language from one precise theory source, choosing independent practice, reviewing a learner solution, debugging, spaced…
event-driven-architecture
Event-Driven Architecture Review: Reviews and designs event-driven systems — Event Sourcing, CQRS, Saga patterns, Domain Events, message brokers, and eventual consistency. Use when the user mentions events, event sourcing, CQRS, saga, choreography vs orchestration, Kafka architecture, event store, projections, read…