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/inspect-running-chronicle/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/inspect-running-chronicle)<a href="https://agentmods.dev/skills/cratis/verticalslices/inspect-running-chronicle"><img src="https://agentmods.dev/badge/skills/cratis/verticalslices/inspect-running-chronicle/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/inspect-running-chronicle"><img src="https://agentmods.dev/badge/skills/cratis/verticalslices/inspect-running-chronicle.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.00106 | $0.01082 |
| Opus 5 | $0.00053 | $0.00541 |
| Sonnet 5 | $0.00021 | $0.00216 |
| Haiku 4.5 | $0.00011 | $0.00108 |
Grade A, and why
inspect-running-chronicle scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- **observable-query-curl** — for exercising an application's own observable query endpoints over HTTP, which is a different surface from the store's management API. This is a copy
100% identical to inspect-running-chronicle — 16 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Inspect a Running Chronicle
Source code says what should happen. When the question is what is happening in a live store — a projection that will not move, an observer that stopped, an event you are not sure was appended — read the server instead of the code. The cratis CLI is how.
Do not guess command names from this file. The CLI ships its own complete, versioned catalog and that is the authority:
cratis llm-context # every command, option and argument as JSON
cratis <group> --help # the same, one group at a time
This skill covers when to reach for the CLI and how to read what comes back. The catalog covers what to type.
Setting it up in a project
Once per project, so every agent working it can reach the store:
cratis init # detects the AI tools in use and writes CHRONICLE.md + a chronicle-cli skill
cratis init --refresh # re-capture after upgrading the CLI
Two things worth knowing before running it:
- The embedded catalog is a snapshot, not a live lookup. After a CLI upgrade it still describes the older surface;
cratis initreports the mismatch and--refreshfixes it. - If the repository's instruction file (
AGENTS.md,CLAUDE.md,.github/copilot-instructions.md) is generated from a shared corpus and propagated — as it is in every repository consuming this one — pass--no-context. Appending to a generated file works until the next sync silently removes it. Add the@CHRONICLE.mdline to the canonical source instead.
Reaching the right server
Resolution order is --server → CHRONICLE_CONNECTION_STRING → the active context → chronicle://localhost:35000. Prefer a named context over repeating a connection string:
cratis context create dev --server chronicle://localhost:35000
cratis context set dev
Be deliberate about which store you are pointed at. The same commands read production and a local container, and several of them are destructive. Confirm the context before running anything that writes.
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 First seen · 72 lines · 106 tokens per session scan A d896c80b4a95
inspect-running-chronicle is a skill published in the GitHub repository Cratis/VerticalSlices (2 stars, last pushed 5d ago), licensed MIT. It adds 106 tokens to every session and 1,082 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). It is 100% identical to inspect-running-chronicle, differing in 16 lines, and is treated as a copy.
Other skills, from other repositories
cratis-cli-terminal-workbench
Navigate the cratis CLI's terminal Workbench - the full-screen TUI launched with cratis chronicle workbench. Use when exploring a running Chronicle store interactively rather than answering one question with a single command, when locating an observer, failure, event type, projection or read model by name, or when…
cratis-chronicle-web-workbench
Use the Chronicle browser Workbench - its screens, what each one can read and change, how it is reached and enabled, and the operational discipline for redaction, revision, replay, quarantine clearing and kernel reset. Use when inspecting or operating a running Chronicle store through the browser, or when deciding…
review-performance
Use this skill when asked to check for performance issues, inefficiencies, or scalability problems in a Cratis-based project. Covers Chronicle projections, MongoDB query patterns, .NET allocations, and React render overhead.
cratis-lens-browser-extension
Use the Cratis Lens browser extension against a running Cratis Arc application — building and side-loading it, what the Arc app must already serve for Lens to work, switching the active user and tenant, and executing a command or query from the popup. Use when setting Lens up, when Lens does not detect an Arc app, or…
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…
cratis-arc-ef-core-migration
Change an Entity Framework Core schema in a Cratis Arc application — the DbContext base types Arc provides, the cross-database column helpers, JSON columns, how a migration is created and applied, and how an EF Core read model becomes injectable into a command. Use when adding or changing a table, column…