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-chronicle-event-specificationsgit 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-chronicle-event-specifications)<a href="https://agentmods.dev/skills/cratis/ai/cratis-chronicle-event-specifications"><img src="https://agentmods.dev/badge/skills/cratis/ai/cratis-chronicle-event-specifications/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-chronicle-event-specifications"><img src="https://agentmods.dev/badge/skills/cratis/ai/cratis-chronicle-event-specifications.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.00078 | $0.02182 |
| Opus 5.5 | $0.00031 | $0.00873 |
| Sonnet 5.5 | $0.00016 | $0.00436 |
| Haiku 4.5 | $0.00008 | $0.00218 |
Grade A, and why
cratis-chronicle-event-specifications 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 6d 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 — 229 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Chronicle event specifications
EventScenario runs the append path in-process. No Chronicle server, no
database, no network — an empty event log at sequence number zero, with the
application's constraints discovered and active.
Verified product sources
| Package | Purpose |
|---|---|
Cratis.Chronicle.Testing |
EventScenario, its Given/When builders, the IAppendResult Should* assertions |
Cratis.Chronicle |
IEventSequence.Append/AppendMany, IAppendResult, ConstraintViolation |
Sources: Source/Clients/Testing/EventSequences/, TestingEventStore.cs,
and Source/Clients/DotNET/EventSequences/.
dotnet add package Cratis.Chronicle.Testing
Reverify against the Chronicle repository before claiming support for another version. Never translate an assertion name from memory.
Route near misses
- The behavior is a command running through validators,
Provide()andHandle(): usecratis-application-slice-specifications. - The behavior is a projection or reducer building a read model: use
cratis-chronicle-read-model-specifications. - You are deciding what the constraint should be: use
cratis-chronicle-event-constraints. - The specification style itself — folder shape, naming, what not to specify:
use
cratis-specification-by-example.
When you need this
- A constraint must reject a duplicate or conflicting append.
- A batch append (
AppendMany) must behave as one unit. - The event log's own behavior is the subject, not the command that reached it.
When you do not
- Concurrency violations are not what the scenario's defaults exercise.
EventScenariowires a strategy that always answersConcurrencyScope.None, which the validator skips, so an append that lets the strategy pick the scope (When, orEventLog.Appendwithout aconcurrencyScope) can never reportHasConcurrencyViolations. Only an append that passes an explicit scope onscenario.EventLog.Append(...)reaches the in-process validator at all — and that is a spec of the scope you hand-built, not of the application's strategy. Specify concurrency against the real kernel with an out-of-process integration specification, and do not write a scenario specification that looks like it covers it — it would pass vacuously, which is worse than not having one.
What ships with it
1 file 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.
- 6d ago Changed · +7 lines d3f8fc7f2721
- 7d ago Changed 0095e78bcc87
- 9d ago Changed · +13 lines daf3e2f0e0b0
- 15d ago Changed · +2 lines 8b373f384949
- 1mo ago Changed · +6 lines 7e126eadd213
- 1mo ago First seen · 201 lines · 78 tokens per session scan A 64f99ea68ea3
cratis-chronicle-event-specifications is a skill published in the GitHub repository Cratis/AI (4 stars, last pushed yesterday), licensed MIT. It adds 78 tokens to every session and 2,182 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-08.
Other skills, from other repositories
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…