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-specs-typescriptnpx skills add Cratis/AI --skill cratis-specs-typescriptgit 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-specs-typescript)<a href="https://agentmods.dev/skills/cratis/ai/cratis-specs-typescript"><img src="https://agentmods.dev/badge/skills/cratis/ai/cratis-specs-typescript.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.00100 | $0.01056 |
| Opus 5 | $0.00050 | $0.00528 |
| Sonnet 5 | $0.00020 | $0.00211 |
| Haiku 4.5 | $0.00010 | $0.00106 |
Grade A, and why
cratis-specs-typescript 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 4d 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-specs-typescript — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Core philosophy
Same BDD philosophy as C# specs — specs describe behaviors, not implementations. The given() helper + context class mirrors the C# Specification base class: setup is separated from the action, each it() verifies a single outcome.
Step 1 — Create the folder structure
for_<ClassName>/
├── given/
│ └── a_<system>.ts ← reusable context class
├── when_<behavior>/ ← behavior with multiple outcomes
│ ├── with_<condition>.ts
│ ├── without_<condition>.ts
│ └── and_<condition>.ts
└── when_<simple_behavior>.ts ← single outcome = single file
Example:
for_EventsCommandResponseValueHandler/
├── given/
│ └── an_events_command_response_value_handler.ts
├── when_checking_can_handle/
│ ├── with_valid_events_collection.ts
│ ├── with_null_value.ts
│ └── without_event_source_id.ts
└── when_handling/
├── empty_events_collection.ts
└── multiple_events_collection.ts
Step 2 — Write a reusable context class
// for_AuthorService/given/an_author_service.ts
import sinon from 'sinon';
import { AuthorService } from '../../../AuthorService';
export class an_author_service {
eventLog: sinon.StubbedInstance<IEventLog>;
service: AuthorService;
constructor() {
this.eventLog = sinon.createStubInstance(EventLog);
this.service = new AuthorService(this.eventLog);
}
}
Properties are public (unlike C# protected fields) — tests access them via context.propertyName.
Step 3 — Write a spec using given()
// for_AuthorService/when_registering/with_valid_name.ts
import { an_author_service } from '../given/an_author_service';
import { given } from '../../given'; // import from package root
describe('when registering with valid name', given(an_author_service, context => {
beforeEach(async () => {
await context.service.register('John Doe');
});
it('should append an event', () => {
context.eventLog.append.calledOnce.should.be.true;
});
it('should pass the author name', () => {
const call = context.eventLog.append.firstCall;
call.args[1].name.should.equal('John Doe');
});
}));
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.
- 4d ago First seen · 149 lines · 100 tokens per session scan A eb01957bcdca
cratis-specs-typescript is a skill published in the GitHub repository Cratis/AI (2 stars, last pushed yesterday), licensed MIT. It adds 100 tokens to every session and 1,056 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
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.