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 agentmods add skills/cratis/ai/add-projectionnpx skills add Cratis/AI --skill add-projectiongit 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/add-projection)<a href="https://agentmods.dev/skills/cratis/ai/add-projection"><img src="https://agentmods.dev/badge/skills/cratis/ai/add-projection.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 | $0.00068 | $0.01551 |
| Opus 5 | $0.00034 | $0.00776 |
| Sonnet 5 | $0.00014 | $0.00310 |
| Haiku 4.5 | $0.00007 | $0.00155 |
Grade A, and why
add-projection 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- add-projection — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add a Chronicle projection that populates a read model from events.
For reactors (automation / translation), see the
add-reactorskill instead.
Projection — Model-Bound (preferred)
Put projection metadata directly on the read model using attributes. No separate class needed.
[ReadModel]
[FromEvent<SomeEventHappened>] // auto-maps all matching property names
public record <ReadModelName>(
[Key] <IdType> Id, // marks the primary key
<PropType> <PropName>) // auto-mapped from SomeEventHappened
{
public static ISubject<IEnumerable<<ReadModelName>>> All(IMongoCollection<<ReadModelName>> collection) =>
collection.Observe();
}
Attribute reference:
| Attribute | Purpose |
|---|---|
[FromEvent<T>] |
Maps event T onto the read model; matching property names map automatically (AutoMap is on by default — never call .AutoMap()) |
[FromEvent<T>(key: nameof(T.Prop))] |
Same, but uses Prop as the read model key instead of EventSourceId |
[Key] |
Marks the primary key property |
[SetFrom<T>(nameof(T.Prop))] |
Explicitly maps one property from event T |
[AddFrom<T>(nameof(T.Prop))] |
Adds event property value to the read model property |
[SubtractFrom<T>(nameof(T.Prop))] |
Subtracts event property value |
[ChildrenFrom<T>(key: nameof(T.Prop))] |
Projects into a nested child collection |
[Join<T>(on: nameof(Prop), eventPropertyName: nameof(T.EProp))] |
Joins data from a related event |
[RemovedWith<T>] |
Marks the instance as removed when event T is appended |
Critical rules:
- Joins must be on Chronicle events — NEVER join on a read model type
- If property names between event and read model match,
[FromEvent<T>]alone is sufficient - Child types also support all attributes recursively
Projection — Fluent / declarative (fallback for complex cases)
Use IProjectionFor<T> only when the projection logic is too complex for model-bound attributes or would become less clear if forced into attributes.
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.
- 3d ago First seen · 104 lines · 68 tokens per session scan A e6c53b655a68
add-projection is a skill published in the GitHub repository Cratis/AI (2 stars, last pushed today), licensed MIT. It adds 68 tokens to every session and 1,551 once invoked, about $0.0003 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-08-31.
Other skills, from other repositories
ship-changes
Ship staged or unstaged local changes: create a branch, make logical commits, push to origin, open a PR with the correct description and label, merge it, close the issues it resolves, and delete the branch locally and on origin. Use whenever the user asks to commit, push, create a PR, ship, or land changes.
add-concept
Use this skill when asked to create a strongly-typed domain identifier or value (such as ProjectId, AuthorName, InvoiceNumber) in a Cratis-based project. Produces a ConceptAs record with the correct conversions and sentinel values.
skill-creator
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, update or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
cratis-command
Step-by-step guidance for creating a Cratis Arc command — [Command] record, Handle() method, CommandValidator, proxy generation, and React .use() hook with CommandDialog. Use when adding or creating a command, wiring up a form or button to the backend, working with IEventLog, CommandResult, CommandValidator…
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…
add-traces
Use this skill when asked to add OpenTelemetry tracing to a class in a Cratis Chronicle Kernel project. Produces Traces.cs companion files using the [Span] source-generator pattern from Cratis.Traces, registers IActivitySource as a keyed DI service, and injects it into the target class.