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-client-dotnetgit 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-client-dotnet)<a href="https://agentmods.dev/skills/cratis/ai/cratis-chronicle-client-dotnet"><img src="https://agentmods.dev/badge/skills/cratis/ai/cratis-chronicle-client-dotnet.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.00123 | $0.05214 |
| Opus 5 | $0.00062 | $0.02607 |
| Sonnet 5 | $0.00025 | $0.01043 |
| Haiku 4.5 | $0.00012 | $0.00521 |
Grade A, and why
cratis-chronicle-client-dotnet 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 — 434 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The Chronicle client for .NET
Cratis.Chronicle is a standalone client SDK. A console app, a worker, or a
service constructs a client, asks it for an event store, and appends or observes.
There is no host requirement and no application architecture imposed.
This is not the Arc integration. In an Arc application, Chronicle is wired in for you and commands return events that Arc appends. Everything below is the layer underneath: what an application that is not Arc has to do itself.
Verified product sources
This skill is verified against the Cratis/Chronicle repository at tag
v17.0.1, whose client sources are byte-identical to 16.45.2 for every public
type cited here except the compatibility check noted below.
| Package | Line | Purpose |
|---|---|---|
Cratis.Chronicle |
17.x |
ChronicleClient, IEventStore, [EventType], observers |
Cratis.Chronicle.Connections |
17.x |
ChronicleConnectionString, connection lifecycle |
Cratis.Chronicle.AspNetCore |
17.x |
ASP.NET Core wiring, header/subdomain namespace resolvers |
Cratis.Chronicle.Testing |
17.x |
in-process scenarios |
Cratis.Chronicle.CodeAnalysis |
17.x |
the analyzers, a separate opt-in package |
Take the exact version from nuget.org. The version in source is a 1.0.0
placeholder injected at pack time (Source/Directory.Build.props), so the
repository never carries the real number. Reverify before claiming support for a
version you have not checked.
Which package
dotnet add package Cratis.Chronicle # console / worker service
dotnet add package Cratis.Chronicle.AspNetCore # ASP.NET Core
Cratis.Chronicle.CodeAnalysis is not pulled in by Cratis.Chronicle. Add
it deliberately — it is what warns about the mistakes an event model makes
silently, such as a nullable event property.
Connecting
The smallest real thing
using Cratis.Chronicle;
using Cratis.Chronicle.Connections;
using var client = new ChronicleClient(ChronicleConnectionString.Development);
var eventStore = await client.GetEventStore("<EventStoreName>");
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 · 434 lines · 123 tokens per session scan A 8a42c9d7e488
cratis-chronicle-client-dotnet is a skill published in the GitHub repository Cratis/AI (2 stars, last pushed today), licensed MIT. It adds 123 tokens to every session and 5,214 once invoked, about $0.0006 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
worker-services
Build long-running .NET background services with BackgroundService, Generic Host, graceful shutdown, configuration, logging, and deployment patterns suited to workers and daemons. USE FOR: background services; scheduled workers; hosted services; worker extraction; graceful shutdown, health checks, and service hosting…
aspnet-core
Build, debug, modernize, or review ASP.NET Core applications with correct hosting, middleware, security, configuration, logging, and deployment patterns on current .NET. USE FOR: working on ASP.NET Core apps, services, or middleware; changing auth, routing, configuration, hosting, or deployment behavior; deciding…
minimal-apis
Design and implement Minimal APIs in ASP.NET Core using handler-first endpoints, route groups, filters, and lightweight composition suited to modern .NET services. USE FOR: building new HTTP APIs in ASP.NET Core; creating lightweight microservices; choosing between Minimal APIs and controllers. DO NOT USE FOR…
web-api
Build or maintain controller-based ASP.NET Core APIs when the project needs controller conventions, advanced model binding, validation extensions, OData, JsonPatch, or existing API patterns. USE FOR: working on controller-based APIs in ASP.NET Core; needing controller-specific extensibility or conventions; migrating…
managedcode-communication
Use ManagedCode.Communication when a .NET application needs explicit result objects, structured errors, and predictable service or API boundaries instead of exception-driven control flow. USE FOR: integrating ManagedCode.Communication into services or APIs; replacing exception-driven result handling with explicit…
grpc
Build or review gRPC services and clients in .NET. USE FOR: ASP.NET Core gRPC, protobuf contracts, unary or streaming RPC, gRPC client factory, interceptors, deadlines, cancellation, channel reuse, backend service integration. DO NOT USE FOR: broad browser-facing APIs without gRPC-Web tradeoff review, SignalR realtime…