Borrowing it
Nothing to install: this file belongs to Cratis/VerticalSlices. 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/Cratis/VerticalSlices/main/.ai/skills/edit-cratis-docs/SKILL.mdgit clone --depth 1 https://github.com/Cratis/VerticalSlicesWrote 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/verticalslices/edit-cratis-docs)<a href="https://agentmods.dev/skills/cratis/verticalslices/edit-cratis-docs"><img src="https://agentmods.dev/badge/skills/cratis/verticalslices/edit-cratis-docs/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/verticalslices/edit-cratis-docs"><img src="https://agentmods.dev/badge/skills/cratis/verticalslices/edit-cratis-docs.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.00104 | $0.00887 |
| Opus 5.5 | $0.00042 | $0.00355 |
| Sonnet 5.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 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.
This is a copy
100% identical to edit-cratis-docs — 60 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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.
- 1mo ago First seen · 51 lines · 104 tokens per session scan A edc005bf722c
edit-cratis-docs is a skill published in the GitHub repository Cratis/VerticalSlices (2 stars, last pushed 1mo ago), licensed MIT. It adds 104 tokens to every session and 887 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to edit-cratis-docs, differing in 60 lines, and is treated as a copy.
Other skills, from other repositories
cratis-screenplay-command-surface
Write the write side of a Cratis Screenplay .play model — the command block and its identifier, reads, validate, authorize, produces, handler and concurrency clauses, plus event, constraint, policy, persona, concept, type and seed. Use when declaring or changing a command, an event shape, a validation or authorization…
cratis-screenplay-read-surface
Declare the read side of a Cratis Screenplay .play model — the readmodel shape, query with by/filter/scoped to/observable/performer, and screen at its three levels of detail, including the data/action contract that later component bindings, templates, forms, toolbars, routes and outlets consume. Use when adding or…
cratis-screenplay-ui-composition
Compose the user interface of a Cratis Screenplay .play model — layout and responsive arrangement, screen/dialog templates, component data-context bindings, exposed template configuration, command forms and columns, navigation contributions, application navigation regions (topbar/sidebar, module…
cratis-arc-authentication-authorization-and-identity
Wire authentication, authorization and identity in a Cratis Arc application — IProvideIdentityDetails and the /.cratis/me endpoint, Arc's [Authorize]/[Roles]/[AllowAnonymous] attributes and named policies, fallback baselines, observable-query emission guards, IAuthenticationHandler, the Microsoft Identity Platform…
cratis-arc-command-execution
Execute an existing Cratis Arc command from backend code through ICommandPipeline — the scopeless and scoped overloads, the typed generic Execute, the pre-flight Validate, validation severity filtering, and how to read CommandResult. Use when a reactor, background job, scheduled task, or backend service must run a…
cratis-arc-command
Define a Cratis Arc command — the [Command] record, its Handle() method and return shape, the optional Provide() step, and the generated TypeScript proxy. Use when adding a command, choosing what Handle() should return, deciding which values may reach the causation chain (including API keys and other credentials…