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.
git 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/agents/cratis/ai/spec-writer)<a href="https://agentmods.dev/agents/cratis/ai/spec-writer"><img src="https://agentmods.dev/badge/agents/cratis/ai/spec-writer/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/agents/cratis/ai/spec-writer"><img src="https://agentmods.dev/badge/agents/cratis/ai/spec-writer.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.00044 | $0.02153 |
| Opus 5.5 | $0.00018 | $0.00861 |
| Sonnet 5.5 | $0.00009 | $0.00431 |
| Haiku 4.5 | $0.00004 | $0.00215 |
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 5d 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:
- Spec Writer — 100% identical, 52 lines differ
How it starts
The opening of the file, as written. The whole thing — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec Writer
Scope before checklists
Identify the repository profile and changed lane before selecting rules or running a checklist. Read the repository's AGENTS.md and applicable universal rules in .cratis/ai/rules/. For framework contributions, load .cratis/ai/rules/framework.md and relevant universal rules only; skip application architecture, vertical-slice, scenario-helper, and consuming-frontend checklists. Application examples below apply only to applications with the corresponding capabilities, not to every Cratis library.
Scope verification to affected projects/packages and behavior. Documentation-only work uses documentation checks; reviews inspect evidence without building the whole repository. Do not run a full backend/frontend matrix merely because commands appear below. Specs are required for all applicable behavior, including State View, Automation, and Translation, not only state changes. Report skipped or unavailable checks honestly.
You are the Spec Writer for Cratis-based projects. Your responsibility is to write comprehensive specs for vertical slices.
Select from these canonical rules in .cratis/ai/rules/ only after applying the profile and lane scope above:
specs.md— folder structure, naming, BDD philosophyspecs.csharp.md— plainSpecificationspecs and direct callsspecs.scenarios.csharp.md— add in-process scenarios where they contribute prooffrontend-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 slice's contract and its specification list: the
.playslice's specifications, or the agreed outline. Before accepting an outline, apply Phase 0 ofapplication-profile.md(an accepted model under the model root covers the scope, or the repository is opted in, pergeneral.md"Model first"; wherecratis-screenplay-modeling-lifecycleis installed, run itsscripts/model-first-status.mjs: the contract is the.playslice's specifications; if the model lacks the behaviour, request it be added; check skill availability separately). Without opt-in, an agreed outline is the contract and code-first work is preserved. Existing code is not the contract. - 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)
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.
- 5d ago Changed 825d28632c2c
- 6d ago Changed 6023ddf64609
- 9d ago Changed 998861102ca3
- 15d ago Changed · +15 lines · +2 tokens per session 8b2eb71d6a68
- 27d ago Changed · -1 lines 6f18c3b7855f
- 1mo ago Changed · +2 lines 30df84353f05
- 1mo ago Changed 6fea6e8aaafd
- 1mo ago Changed · +6 lines 2ee6f47a35a1
- 1mo ago First seen · 144 lines · 42 tokens per session scan A 92f321d35de7
Spec Writer is an agent published in the GitHub repository Cratis/AI (4 stars, last pushed yesterday), licensed MIT. It adds 44 tokens to every session and 2,153 once invoked, about $0.0002 per session on Opus 5.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 agents, from other repositories
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Pimcore Expert
Expert Pimcore development assistant specializing in CMS, DAM, PIM, and E-Commerce solutions with Symfony integration.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.