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-cli-operationsgit 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-cli-operations)<a href="https://agentmods.dev/skills/cratis/ai/cratis-chronicle-cli-operations"><img src="https://agentmods.dev/badge/skills/cratis/ai/cratis-chronicle-cli-operations.svg" alt="Measured on agentmods" 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.00092 | $0.02256 |
| Opus 5 | $0.00046 | $0.01128 |
| Sonnet 5 | $0.00018 | $0.00451 |
| Haiku 4.5 | $0.00009 | $0.00226 |
Grade A, and why
cratis-chronicle-cli-operations 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 today.
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 — 200 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Operate a running Chronicle with the cratis CLI
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.
Verified product sources
This skill is verified against these exact sources:
| Package | Version | Purpose |
|---|---|---|
Cratis.Cli |
2.4.0 |
the cratis command, its contexts, output formats, and command tree |
Cratis.Chronicle |
16.45.2 |
the observer, partition, sequence, and job concepts the CLI reads |
The CLI ships a versioned machine-readable catalog of its own surface, and that catalog is the authority for exact command names on the installed version:
cratis llm-context # every command, option and argument as JSON
cratis llm-context --schema # the JSON Schema for that document
cratis <group> --help # the same, one group at a time
Do not guess a command name from this file. This skill covers when to reach for the CLI and how to read what comes back; the catalog covers what to type.
Install and set up
cratis is a .NET tool published as Cratis.Cli with the command name
cratis. Install it with dotnet tool install -g Cratis.Cli, or through
Homebrew, or from a release binary. Follow with cratis completions install.
Once per project, so every agent working it can reach the store:
cratis init # detects the AI tools in use and writes project context
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 is supplied by a shared package or a
generated adapter, pass
--no-context. Keep project-specific Chronicle connection guidance in a repository-owned project context file; never patch packaged or generated bytes.
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.
- today First seen · 200 lines · 92 tokens per session scan A 52047e93065a
cratis-chronicle-cli-operations is a skill published in the GitHub repository Cratis/AI (2 stars, last pushed today), licensed MIT. It adds 92 tokens to every session and 2,256 once invoked, about $0.0005 per session on Opus 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
managedcode-orleans-graph
Integrate ManagedCode.Orleans.Graph into an Orleans-based .NET application for grain-call policy enforcement, deadlock detection, live-call telemetry, and Mermaid graph diagnostics. USE FOR: ManagedCode.Orleans.Graph integration; allowed grain transitions; Orleans call filters; live policy graphs; reviewing Orleans…
asynkron-profiler
Use the open-source free Asynkron.Profiler dotnet tool for CLI-first CPU, allocation, exception, contention, and heap profiling of .NET commands or existing trace artifacts. USE FOR: Asynkron.Profiler setup; automation-friendly profiling output; CPU, allocation, exception, contention, and heap investigation. DO NOT…
maui-ai-debugging
Legacy DevFlow debug skill. USE FOR: maui-ai-debugging, maui devflow, screenshots, visual tree, Blazor CDP, simulator/emulator debugging. DO NOT USE FOR: setup, desktop automation, AppleScript, host xdotool.
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.
fix-feature-bug
Skill "fix-feature-bug" from markmhendrickson/neotoma, covering fix feature bug, workflow, error classification (configurable), configuration and inputs.
analyzing-code-structure
Use when editing code structure with text matching ambiguity, handling "oldstring not unique" problems, or performing formatting-independent pattern matching across function signatures, method calls, and class structures.