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/review-codenpx skills add Cratis/AI --skill review-codegit clone --depth 1 https://github.com/Cratis/AIWhat 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.00044 | $0.01113 |
| Opus 5 | $0.00022 | $0.00557 |
| Sonnet 5 | $0.00009 | $0.00223 |
| Haiku 4.5 | $0.00004 | $0.00111 |
Grade A, and why
review-code 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- review-code — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review changed code against all Cratis project standards and produce a structured report.
C# Architecture
- Each slice is its own folder
<Module>/<Feature>/<Slice>/<Slice>.cswith all backend artifacts — no top-levelFeatures/wrapper - Commands:
recordtype withHandle()directly on them — no separate handler classes - Business rejection returns a
ValidationResult/Result<TEvent, ValidationResult>(or validator) — never thrown fromProvide()/Handle()(a throw is HTTP 500, not a validation error) - Fetched/computed handler data is in
Provide(), not inline inHandle() - Events:
recordtype, no mutable/nullable properties, past tense, never carry the event-source id - Identity concepts derive from
EventSourceId<T>(notConceptAs<Guid>) - Projections: AutoMap is on by default —
.AutoMap()only after.NoAutoMap(); projections consume events, never read models - Model-bound query custom paths use
[Path("...")], not[Route] - No service locator (
IServiceProvidernot injected); discover implementations withIInstancesOf<T>, notIEnumerable<T> - Namespace matches folder under the app source root (
<RootNamespace>.<Module>.<Feature>.<Slice>)
C# Code Style
- File-scoped namespaces;
usingdirectives alphabetically sorted - No unused
usingdirectives -
is null/is not null— never== null/!= null -
varpreferred over explicit types - No postfixes:
Async,Impl,Serviceon class names - No regions
- All public types, methods, and properties have multiline XML doc comments
-
<summary>tags always multiline — never/// <summary>Text</summary>on one line - Methods with parameters include
<param name="...">for each - Non-void methods include
<returns> - Custom exception types only — never
InvalidOperationException,ArgumentException, etc. - Exception XML docs start with "The exception that is thrown when …"
- Copyright header on every file
- Strongly-typed Concepts for all domain IDs/values (no raw
Guid/stringin domain models)
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.
- yesterday First seen · 87 lines · 44 tokens per session scan A 6cd509452e8e
review-code is a skill published in the GitHub repository Cratis/AI (2 stars, last pushed 4d ago), licensed MIT. It adds 44 tokens to every session and 1,113 once invoked, about $0.0002 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…
auth-and-identity
Use this skill for authentication, authorization, or identity in a Cratis Arc project — backend, frontend, or both. Covers identity providers (IProvideIdentityDetails), protecting commands/queries with authorization attributes, Microsoft Identity Platform, connecting backend identity to React, multi-tenant identity…