Borrowing it
Nothing to install: this file belongs to Cratis/VerticalSlices. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Cratis/VerticalSlices/main/.ai/skills/cratis-specs-typescript/SKILL.mdgit clone --depth 1 https://github.com/Cratis/VerticalSlicesWrote 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/verticalslices/cratis-specs-typescript)<a href="https://agentmods.dev/skills/cratis/verticalslices/cratis-specs-typescript"><img src="https://agentmods.dev/badge/skills/cratis/verticalslices/cratis-specs-typescript/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/verticalslices/cratis-specs-typescript"><img src="https://agentmods.dev/badge/skills/cratis/verticalslices/cratis-specs-typescript.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.00100 | $0.01056 |
| Opus 5.5 | $0.00040 | $0.00422 |
| Sonnet 5.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 1mo 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.
This is a copy
100% identical to cratis-specs-typescript — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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.
- 1mo ago First seen · 149 lines · 100 tokens per session scan A eb01957bcdca
cratis-specs-typescript is a skill published in the GitHub repository Cratis/VerticalSlices (2 stars, last pushed 1mo ago), licensed MIT. It adds 100 tokens to every session and 1,056 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to cratis-specs-typescript, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
vitest
Vitest testing framework patterns for test setup, async testing, mocking with vi., snapshots, and test performance (formerly test-vitest). This skill should be used when writing or debugging Vitest tests. This skill does NOT cover TDD methodology (use test-tdd skill), API mocking with MSW (use test-msw skill), or…
cratis-chronicle-client-typescript
Connect Node.js applications to Chronicle with @cratis/chronicle, including reflect-metadata, compiler settings, camelCase reactor dispatch, projections, reducers, variants and the lazy-connect lifecycle. Use when configuring @cratis/chronicle decorators, glob discovery or eventLog.append in a standalone Node.js…
cratis-arc-command-typescript
Define a Cratis Arc command in a Node.js TypeScript server with Arc for TypeScript — project setup from the source preview, ArcApplication.createBuilder() and discovery, the @command() class with @field inputs, handle() and provide(), outcome helpers, service injection, authorization, returning Chronicle events…
cratis-arc-query-typescript
Expose Arc for TypeScript server reads with argument binding, queryPage paging, storage adapters, authorization and query scenarios. Use when declaring Node.js @readModel()/@query() methods or RxJS observable endpoints over SSE/WebSocket. Do not use for JVM companion/static methods (use cratis-arc-query-kotlin), C#…
cratis-arc-validation-typescript
Add rejection checks to Arc for TypeScript servers, including proxy-safe rules and severity filtering. Use when authoring Node.js ruleFor chains, readModelForValidation checks or rejected()/denied() outcomes in provide()/handle(), and asserting them with @cratis/arc.testing. Do not use for C# validation (use…
cratis-arc-testing-kotlin
Specify Kotlin or Java Arc commands and queries through real in-process pipelines with arc-testing — CommandScenario, QueryScenario, bounded ObservableQueryScenario collection, read-model pins, tenant resolution, and Chronicle append assertions. Use when writing or diagnosing JVM Arc pipeline specifications without…