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/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-cli-operations"><img src="https://agentmods.dev/badge/skills/cratis/ai/cratis-chronicle-cli-operations.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.00092 | $0.03609 |
| Opus 5.5 | $0.00037 | $0.01444 |
| Sonnet 5.5 | $0.00018 | $0.00722 |
| Haiku 4.5 | $0.00009 | $0.00361 |
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 yesterday.
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 — 272 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 draws on these sources:
| Package | Purpose |
|---|---|
Cratis.Cli |
command effects, confirmations, contexts, output and command tree |
Cratis.Chronicle |
the CLI's Chronicle client package; server authentication configuration and development-client registration |
Observer removal, partition-quarantine clearing, server-bound login and diagnose scope are operational. Read command effects when classifying a mutation or confirmation.
The CLI ships a versioned machine-readable catalog of its own surface, and
that catalog is the authority for exact command names, effect and
requiresConfirmation on the installed version. Treat every effect other than
read-only (including unknown values) as a state change:
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
2 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.
- yesterday Changed · +4 lines 9c008ecbc437
- 7d ago Changed · -3 lines 11fd5298d43c
- 9d ago Changed · +54 lines 8f361a132460
- 20d ago Changed · +4 lines 3bfc463c7734
- 27d ago Changed · +7 lines b60067af0275
- 1mo ago Changed · +6 lines 28a2961920a7
- 1mo ago 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 (4 stars, last pushed yesterday), licensed MIT. It adds 92 tokens to every session and 3,609 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
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…