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/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-client-dotnet"><img src="https://agentmods.dev/badge/skills/cratis/ai/cratis-chronicle-client-dotnet.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.00123 | $0.03662 |
| Opus 5.5 | $0.00049 | $0.01465 |
| Sonnet 5.5 | $0.00025 | $0.00732 |
| Haiku 4.5 | $0.00012 | $0.00366 |
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 3d 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 — 310 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
Source: Cratis/Chronicle.
| Package | Purpose |
|---|---|
Cratis.Chronicle |
ChronicleClient, IEventStore, [EventType], existing observers; reducer discovery and nomination (DefaultClientArtifactsProvider.cs, Reducers/{SelfReducerMethods,RegisteredReducerReadModel,ReducerCatalog}.cs, Registrations/ExplicitArtifacts.Types.cs) |
Cratis.Chronicle.Connections |
ChronicleConnectionString, connection lifecycle |
Cratis.Chronicle.AspNetCore |
ASP.NET Core wiring, header/subdomain namespace resolvers |
Cratis.Chronicle.Testing |
in-process scenarios |
Cratis.Chronicle.CodeAnalysis |
CHR analyzers, distributed as a client dependency |
Take the version from nuget.org, not the placeholder version in the source.
Read references/occurrences.md when recording durable triggers, implementing occurrence handlers, or choosing startup/shutdown activation and retry semantics. Read references/immediate-append-refusal.md when a unit must prevent immediate appends from escaping its atomic receipt boundary before transport.
Lifecycle
Read references/lifecycle.md when waiting for registration (WaitForRegistration, not polling IsConnected), diagnosing quiet observers (keepalive loss fails silently, not with an exception), or disposing the client.
What a standalone app owns that a host would have supplied
Every one of these has a silent default. Read them as a checklist, because the
defaults are reasonable for a sample and wrong for a service
(ChronicleClient.cs, options constructor):
What ships with it
11 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.
- LICENSE 142 B
- references/additional-surfaces.md 5.0 KB
- references/client-construction.md 2.0 KB
- references/compatibility-check.md 2.0 KB
- references/connection-options.md 3.3 KB
- references/discovery.md 8.7 KB
- references/hosting.md 3.2 KB
- references/immediate-append-refusal.md 2.2 KB
- references/lifecycle.md 2.6 KB
- references/occurrences.md 4.6 KB
- references/pinned-generation-delivery.md 5.5 KB
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.
- 3d ago Changed · +5 lines e3b4d47f5e1c
- 7d ago Changed · -94 lines fe9f843fb379
- 9d ago Changed · -12 lines d4e1af4f83dd
- 10d ago Changed · +14 lines acb3931c5a4c
- 12d ago Changed · -64 lines f47144b56e7a
- 15d ago Changed · +25 lines eddea41d8e37
- 20d ago Changed 4ff7ffd37ad0
- 1mo ago Changed · +2 lines 5be61ab30438
- 1mo ago 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 (4 stars, last pushed yesterday), licensed MIT. It adds 123 tokens to every session and 3,662 once invoked, about $0.0005 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
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…
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…
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…
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…
managedcode-storage
Use ManagedCode.Storage when a .NET application needs a provider-agnostic storage abstraction with explicit configuration, container selection, upload and download flows, and backend-specific integration kept. USE FOR: integrating ManagedCode.Storage into a .NET application; reviewing how a project abstracts file or…
add-slice
Scaffold a slice in this Vertical Slice Architecture template — one use case in its own folder, with its FastEndpoints endpoint, request, response, validator, and summary, plus the Feature and Group if they don't exist yet, plus tests. Use when the user says "add a slice", "add a use case", "add an endpoint", "add a…