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 skills/cratis/ai/edit-cratis-docsnpx skills add Cratis/AI --skill edit-cratis-docsgit clone --depth 1 https://github.com/Cratis/AIWhat 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.00104 | $0.00887 |
| Opus 5 | $0.00052 | $0.00443 |
| Sonnet 5 | $0.00021 | $0.00177 |
| Haiku 4.5 | $0.00010 | $0.00089 |
Grade A, and why
edit-cratis-docs 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 2d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- edit-cratis-docs — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Editing a Cratis documentation page
Scope this skill to source files under
Documentation/**in the product or contributing repo. Site-level pages inDocumentation/webare owned by the Documentation repo.
Cratis docs content lives in each product's own repo under that repo's Documentation/ folder; the published site (in the Documentation repo at Documentation/web/) aggregates them. Editing the wrong copy wastes the work — the per-product folders under web/src/content/docs/ are generated and overwritten.
1. Find the source of truth
Map the page URL to its owning repo:
| URL | Source file |
|---|---|
/chronicle/** |
Chronicle/Documentation/** |
/arc/** |
Arc/Documentation/** (the ApplicationModel repo, cloned as Arc) |
/components/** |
Components/Documentation/** |
/cli/**, /fundamentals/**, /contributing/** |
the matching repo's Documentation/ |
/, /why-cratis, /cratis-stack, /glossary, /comparisons/**, /adopting-cratis, … |
Site-level pages: use the Documentation repo; source lives in Documentation/web/src/content/docs/*.{md,mdx}. |
Example: /chronicle/concepts/event-source/ → Chronicle/Documentation/concepts/event-source.md. If unsure, grep -rl "<a distinctive sentence>" */Documentation Documentation/web/src/content/docs/*.md*.
Never edit Documentation/web/src/content/docs/{chronicle,arc,components,cli,fundamentals,contributing}/ — generated and git-ignored.
2. Edit the source
- Match the page's Diátaxis type (tutorial / how-to / explanation / reference) and the tour voice (teach, don't dump) — see the
writing-cratis-docsrule (the tour-voice checklist + Starlight authoring tools). Don't mix types. - Verify every framework API in a code example against real source before writing it — readers paste them verbatim. (See the
writing-correct-examplesrule; grep Studio*.cs/*.tsxand the productSource/trees.) - Link rules: product
.mdmay use./foo.md; links to a.mdxpage must be extension-less (./foo); site-level.mdxuses clean root-relative URLs (/arc/...).
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.
- 2d ago First seen · 51 lines · 104 tokens per session scan A edc005bf722c
edit-cratis-docs is a skill published in the GitHub repository Cratis/AI (2 stars, last pushed 4d ago), licensed MIT. It adds 104 tokens to every session and 887 once invoked, about $0.0005 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 skills, from other repositories
ship-changes
Ship staged or unstaged local changes: create a branch, make logical commits, push to origin, open a PR with the correct description and label, merge it, close the issues it resolves, and delete the branch locally and on origin. Use whenever the user asks to commit, push, create a PR, ship, or land changes.
add-concept
Use this skill when asked to create a strongly-typed domain identifier or value (such as ProjectId, AuthorName, InvoiceNumber) in a Cratis-based project. Produces a ConceptAs record with the correct conversions and sentinel values.
skill-creator
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, update or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
auth-and-identity
Use this skill for authentication, authorization, or identity in a Cratis Arc project — backend, frontend, or both. Covers identity providers (IProvideIdentityDetails), protecting commands/queries with authorization attributes, Microsoft Identity Platform, connecting backend identity to React, multi-tenant identity…
cratis-command
Step-by-step guidance for creating a Cratis Arc command — [Command] record, Handle() method, CommandValidator, proxy generation, and React .use() hook with CommandDialog. Use when adding or creating a command, wiring up a form or button to the backend, working with IEventLog, CommandResult, CommandValidator…
cratis-readmodel
Step-by-step guidance for creating a Cratis Chronicle read model from scratch — defining events, choosing between projection and reducer, [ReadModel] record with static query methods, and the generated TypeScript proxy in React. Use when creating a read model, working with [EventType], [ReadModel], IProjectionFor…