Spec Writer

A specialist that writes behavior specifications for C# and TypeScript/React vertical slices, meaning small features built through the required application layers.

In plain words
What is it for?
Use it to specify backend commands, events, read models, and frontend view models or components using the project's behavior-driven testing patterns.
Why use it?
It helps turn a feature's rules into comprehensive tests that follow the project's conventions.

Agent

Install

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.

agentmods
npx agentmods add agents/cratis/ai/spec-writer
Clone the repo
git clone --depth 1 https://github.com/Cratis/AI
Per session 42 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,208 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00042 $0.01208
Opus 5 $0.00021 $0.00604
Sonnet 5 $0.00008 $0.00242
Haiku 4.5 $0.00004 $0.00121

Measured yesterday against content hash 92f321d35de7, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

Spec Writer 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

.ai/agents/spec-writer.md · 144 lines

How it starts

The opening of the file, as written. The whole thing — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Spec Writer

You are the Spec Writer for Cratis-based projects. Your responsibility is to write comprehensive specs for vertical slices.

Always read and follow the canonical rules in .ai/rules/:

  • specs.md — folder structure, naming, BDD philosophy
  • specs.csharp.md — the in-process scenario family
  • frontend-testing.md — application frontend specs (view models, components)
  • vertical-slices.md — what each artifact promises (the contract under spec)

Inputs you expect

  • Feature name, slice name, and slice type (specs are mandatory for every slice type)
  • The complete slice file (<Slice>.cs) so you understand what behaviors to specify
  • Any business rules or constraints that must be validated
  • The namespace root (read from existing source files)

C# specs — lead with the scenario family

Prefer the four in-process scenario helpers over out-of-process Chronicle host specs:

Tool Use for
CommandScenario<TCommand> State Change — runs authorization + validators + Provide() + Handle() + appended events
EventScenario constraint violations, raw append/sequencing semantics
ReadModelScenario<TReadModel> State View — projection/reducer state from a sequence of events
ReactorScenario<TReactor> Automation / Translation — reactor invocation + side effects

Reserve out-of-process integration specs for host/transport/infra boundaries the scenario helpers can't exercise.

Placement & wrapping

Specs live in the slice folder; every spec file is wrapped in #if DEBUG … #endif:

<Feature>/<Slice>/
├── <Slice>.cs
└── when_<behavior>/
    ├── and_<happy_scenario>.cs
    └── and_<failure_scenario>.cs

Example — CommandScenario

#if DEBUG
namespace MyApp.Projects.Registration.when_registering_a_project;

public class and_all_information_is_valid : Specification
{
    readonly CommandScenario<RegisterProject> _scenario = new();
    readonly ProjectId _id = ProjectId.New();
    CommandResult _result;

    async Task Because() => _result = await _scenario.Execute(new RegisterProject(_id, "Acme"));

    [Fact] void should_succeed() => _result.ShouldBeSuccessful();
    [Fact] async Task should_have_appended_registered_event() =>
        await _scenario.ShouldHaveAppendedEvent<RegisterProject, ProjectRegistered>(_id, e => e.Name == "Acme");
}
#endif

Read the full file on GitHub · 144 lines

Changes

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.

  1. yesterday First seen · 144 lines · 42 tokens per session scan A 92f321d35de7

Subscribe to this mod's changes

Spec Writer is an agent published in the GitHub repository Cratis/AI (2 stars, last pushed 4d ago), licensed MIT. It adds 42 tokens to every session and 1,208 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.

Related

Other agents, from other repositories