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/cratis-csharp-standardsnpx skills add Cratis/AI --skill cratis-csharp-standardsgit 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-csharp-standards)<a href="https://agentmods.dev/skills/cratis/ai/cratis-csharp-standards"><img src="https://agentmods.dev/badge/skills/cratis/ai/cratis-csharp-standards.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.00101 | $0.00728 |
| Opus 5 | $0.00051 | $0.00364 |
| Sonnet 5 | $0.00020 | $0.00146 |
| Haiku 4.5 | $0.00010 | $0.00073 |
Grade A, and why
cratis-csharp-standards 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:
- cratis-csharp-standards — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Key rules (quick reference)
- Use C# 13 features always — records, primary constructors, pattern matching
varover explicit types — the right side already tells you the type- File-scoped namespace declarations — one less indentation level
usingdirectives: alphabetically sorted, single-line, unused ones removed- No regions — if a file needs them, it needs refactoring
- No postfixes: no
Async,Impl,Service,Manager,Handleron class names - No
Exceptionsuffix on exception types —AuthorNotFoundnotAuthorNotFoundException - Never use built-in exceptions — always create custom exception types
recordfor events, commands, read models, concepts — value equality for free- Primary constructors for all types — eliminates field boilerplate
is null/is not null— never== null/!= null- Blank line before opening
{of every code block - Final
returnon its own line - Private fields:
_camelCasewith underscore prefix - Interfaces:
Iprefix (IMyService) - No
[EventType]arguments — the type name is the event identifier [Command]records defineHandle()directly — no separate handler classes
Formatting
// File-scoped namespace (no extra indent)
namespace MyApp.Authors.Registration;
// Alphabetically sorted using directives
using Cratis.Arc.Commands;
using Cratis.Chronicle.Events;
using Microsoft.Extensions.Logging;
// Blank line before { of every block
if (condition)
{
DoSomething();
}
// Expression-bodied for simple members
public string FullName => $"{FirstName} {LastName}";
// Final return on its own line
public string GetName()
{
var result = BuildName();
return result;
}
Naming
| Artifact | Convention | Example |
|---|---|---|
| Type / method / public member | PascalCase | RegisterAuthor, AuthorId |
| Private field | _camelCase |
_eventLog |
| Local variable | camelCase | authorId |
| Interface | I prefix |
IEventLog |
| Exception type | No Exception suffix |
AuthorNotFound |
| Feature folder | Pluralized domain noun | Authors/ |
| Concept file | Concept name | AuthorId.cs |
What ships with it
4 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 · 80 lines · 101 tokens per session scan A 15ebd883f5e5
cratis-csharp-standards is a skill published in the GitHub repository Cratis/AI (2 stars, last pushed 5d ago), licensed MIT. It adds 101 tokens to every session and 728 once invoked, about $0.0005 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
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.
cratis-specs-csharp
Step-by-step guidance for writing C# specs in Cratis with BDD Specification by Example — the Establish/Because/should pattern, for/when/and folder hierarchy, reusable given/ contexts, NSubstitute mocking, and the in-process scenario family. Use when writing C# unit or integration specs or structuring the for/when/and…
cratis-csharp-standards
Reference for Cratis C# coding conventions — formatting, naming, records, nullable handling, exceptions, logging, and DI. Use whenever writing C# in a Cratis project, deciding between record vs class, checking naming rules, applying formatting conventions, handling null safety, creating exception types, or asking "how…
cratis-specs-typescript
Step-by-step guidance for writing TypeScript specs in Cratis using BDD-style Specification by Example — the given()/describe/it pattern, for/when/ folder hierarchy, reusable context classes, Sinon mocking, and Chai assertions. Use whenever writing TypeScript specs or tests, creating spec files/folders, using the…
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.
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.