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/write-specs-readmodels/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/write-specs-readmodels)<a href="https://agentmods.dev/skills/cratis/verticalslices/write-specs-readmodels"><img src="https://agentmods.dev/badge/skills/cratis/verticalslices/write-specs-readmodels/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/write-specs-readmodels"><img src="https://agentmods.dev/badge/skills/cratis/verticalslices/write-specs-readmodels.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.00053 | $0.01477 |
| Opus 5.5 | $0.00021 | $0.00591 |
| Sonnet 5.5 | $0.00011 | $0.00295 |
| Haiku 4.5 | $0.00005 | $0.00148 |
Grade A, and why
write-specs-readmodels 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 write-specs-readmodels — 0 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 — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Writing Read Model Specs with ReadModelScenario
Use ReadModelScenario<TReadModel> to test read model projections and reducers entirely in-process — no Chronicle server, database, or network required. Wrap every spec file in #if DEBUG … #endif so spec code ships only in Debug.
When to use this skill
- Testing that a reducer correctly builds state from a sequence of events
- Testing that a fluent
IProjectionFor<T>projection maps event properties to read model properties - Testing that a model-bound projection (
[FromEvent<T>],[Key]) maps correctly - Testing boundary conditions: first event, multiple events, different event sources
For testing event appending, constraints, or concurrency, use EventScenario instead.
Package
dotnet add package Cratis.Chronicle.Testing
Basic structure
// In your spec file (follows BDD Establish/Because/should_ pattern)
public class when_<event_sequence_description> : Specification
{
ReadModelScenario<TReadModel> _scenario;
async Task Establish()
{
_scenario = new ReadModelScenario<TReadModel>();
await _scenario.Given
.ForEventSource(<eventSourceId>)
.Events(new <EventType>(<args>));
}
[Fact] void should_<expected_state>() => _scenario.Instance!.<Property>.ShouldEqual(<expectedValue>);
}
Step 1 — Create the scenario
Always create a new ReadModelScenario<TReadModel> per test. Optionally pass an initial state:
// Default (empty) initial state
var scenario = new ReadModelScenario<MyReadModel>();
// With an initial state baseline
var scenario = new ReadModelScenario<MyReadModel>(new MyReadModel { Count = 10 });
Step 2 — Seed events via the fluent Given builder
await scenario.Given
.ForEventSource(myId)
.Events(new SomeEvent("value"), new SomeOtherEvent(42));
Chain multiple ForEventSource calls to seed different event sources:
await scenario.Given
.ForEventSource(orderId)
.Events(new OrderCreated("order-1"), new ItemAdded(9.99m));
await scenario.Given
.ForEventSource(anotherOrderId)
.Events(new OrderCreated("order-2"));
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 · 217 lines · 53 tokens per session scan A 57d0f2511e95
write-specs-readmodels is a skill published in the GitHub repository Cratis/VerticalSlices (2 stars, last pushed 1mo ago), licensed MIT. It adds 53 tokens to every session and 1,477 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to write-specs-readmodels, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
cratis-application-slice-specifications
Specify the backend behavior of an event-sourced Cratis application slice — plain-call specs for pure decisions, plus CommandScenario, EventScenario, ReadModelScenario and ReactorScenario where the pipeline, validation, constraints or projections matter — including what to cover for each slice type and where the…
cratis-chronicle-event-constraints
Enforce append-time uniqueness in Chronicle with the [Unique] attribute, [RemoveConstraint], and IConstraint, and specify the violation with EventScenario. Use when a rule must hold at the event store rather than in a command, so two concurrent appends cannot both win. Do not use for ordinary command input validation…
cratis-chronicle-read-model-specifications
Specify declarative projections and reducer wiring with ReadModelScenario from Cratis.Chronicle.Testing — seeding events through Given and asserting on the materialized instance; start with Specification plus a direct call for pure reducer decisions. Use when the behavior under specification is how events become…
cratis-chronicle-event-specifications
Specify event-append behavior with EventScenario from Cratis.Chronicle.Testing — seeding prior events through Given, appending through When or the event log, and asserting on the append result including constraint violations. Use when the behavior under specification is what reaches the event store. Do not use for…
cratis-application-react-specifications
Write specifications for the React and TypeScript surface of a Cratis application slice — view models, helpers, command orchestration, and narrow component behavior — using Vitest with Mocha-style describe/it, Sinon, and the Chai should interface. Use when specifying React view-model decisions, frontend command…
vitest
Vitest testing framework patterns for test setup, async testing, mocking with vi., snapshots, and test performance (formerly test-vitest). This skill should be used when writing or debugging Vitest tests. This skill does NOT cover TDD methodology (use test-tdd skill), API mocking with MSW (use test-msw skill), or…