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-type-migrationgit 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-type-migration)<a href="https://agentmods.dev/skills/cratis/ai/cratis-chronicle-event-type-migration"><img src="https://agentmods.dev/badge/skills/cratis/ai/cratis-chronicle-event-type-migration/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-type-migration"><img src="https://agentmods.dev/badge/skills/cratis/ai/cratis-chronicle-event-type-migration.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.00093 | $0.03604 |
| Opus 5.5 | $0.00037 | $0.01442 |
| Sonnet 5.5 | $0.00019 | $0.00721 |
| Haiku 4.5 | $0.00009 | $0.00360 |
Grade A, and why
cratis-chronicle-event-type-migration 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 8d 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 — 318 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Chronicle event type migrations
Chronicle stores events forever. When an event's schema must change, you add a generation and write a migration rather than editing the original record. Chronicle discovers migrations by convention and applies them when reading older events.
You need this only once events of the prior shape exist somewhere you cannot regenerate. Before that — greenfield development with disposable data — rename event types and change schemas freely. A migration written too early is dead code that hides the real schema in the history.
Route near misses
- An accepted
.playmodel under the model root covers the behavior, or the repository is opted in (pergeneral.md"Model first"; wherecratis-screenplay-modeling-lifecycleis installed, run itsscripts/model-first-status.mjs): change the model first withcratis-screenplay-event-modeling. If the Screenplay skills are not installed, say so and do not author.playfrom memory. Edit code here only for infrastructure, clients, adapters, Screenplay code attachments, or gap-fill scope (cratis-screenplay-render-and-gap-fill); never edit Stage-managed output.
Verified product sources
Sources:
| Package | Purpose |
|---|---|
Cratis.Chronicle |
Cratis.Chronicle.Events and Cratis.Chronicle.Events.Migrations |
Cratis.Chronicle.CodeAnalysis |
CHR0012, CHR0037, CHR0049, CHR0050 |
Reverify product sources before claiming support for another version.
Requires Chronicle 19.52.0 for marker-free migration nomination through
ExplicitArtifacts.RegisterMigration<T>(). Read references/explicit-migrations.md
when event endpoints are plain/aliased or a migration cannot reference Chronicle;
check the client package version, since older clients need migration markers.
Generations
Cratis.Chronicle.Events.EventTypeAttribute carries the identity and the
generation:
public sealed class EventTypeAttribute(string id = "", uint generation = 1) : Attribute
What ships with it
3 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.
- 8d ago Changed · +15 lines c0cf47abe2ed
- 10d ago Changed · +2 lines 88d31258e3b9
- 11d ago Changed · +30 lines f4ce9c5de693
- 12d ago Changed · +22 lines d5de0908a60c
- 15d ago Changed b97bf3af5d12
- 17d ago Changed · +13 lines cfb56a42ae6e
- 1mo ago Changed e4574a9c04f8
- 1mo ago First seen · 236 lines · 93 tokens per session scan A fdc57b34be44
cratis-chronicle-event-type-migration is a skill published in the GitHub repository Cratis/AI (4 stars, last pushed today), licensed MIT. It adds 93 tokens to every session and 3,604 once invoked, about $0.0004 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-06.
Other skills, from other repositories
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.
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.
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.