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 skills add Cratis/AI --skill cratis-screenplay-command-surfacegit 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-screenplay-command-surface)<a href="https://agentmods.dev/skills/cratis/ai/cratis-screenplay-command-surface"><img src="https://agentmods.dev/badge/skills/cratis/ai/cratis-screenplay-command-surface/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/ai/cratis-screenplay-command-surface"><img src="https://agentmods.dev/badge/skills/cratis/ai/cratis-screenplay-command-surface.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.00126 | $0.04305 |
| Opus 5.5 | $0.00050 | $0.01722 |
| Sonnet 5.5 | $0.00025 | $0.00861 |
| Haiku 4.5 | $0.00013 | $0.00430 |
Grade A, and why
cratis-screenplay-command-surface 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 325 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The Screenplay write surface
Read preferred syntax when writing or reviewing .play.
Everything that changes the system: the command that expresses intent, the
event it appends, the rules that can refuse it, and the strongly-typed values
they are all built from.
Locate the model
Look first for the project's existing .play files: their folder is the model.
For a new model, check Source/ or src/, else use Screenplay/ at the repository
root. Never put a model under .cratis/ or hand-copy it between repositories.
cratis ai install manages .cratis/ai/, never model files. Keep explanatory
Markdown in project documentation; .play is the single flow model.
Product sources
Tool versions: toolchain SKILL.md; sources below. Compilation is not execution.
- Examples and executable boundaries; inline events, repairs, canonical
optional. handler, code attachments,personaand compliance binding (Semantics/SemanticModelBinder*.cs,Diagnostics/DiagnosticCodes.cs).- Generated-value and response rules (ESM v7).
- Identity and compliance syntax (
identity.md,context.md,concepts.md,purposes.md,events.md,diagnostics.md); v13 compliance admission:references/compliance.md. - v15 generation strategies, strict fixtures and freshness; Stage realization:
references/generated-values-and-responses.md; shop:references/shop-generation.md.
"Parses" and "runs" are different claims. The executable profile, and what
each construct binds to, is in the cratis-screenplay-model-authoring language
reference.
concept and type
concept InvoiceId : Uuid
concept DiscountPercentage : Decimal
validate
>= 0 message "A discount cannot be negative"
<= 100 message "A discount cannot exceed 100 percent"
concept PersonName : String pii
pii reason "Identifies the billing contact."
concept InvoiceStatus : Enum
draft
sent
paid
Primitives: Uuid, String, Int, Decimal, Bool, Date, DateTime.
Enum is a separate concept kind; details: references/enum-numbers.md.
Use bare pii (personal alias) and secret on concepts; Compliance is inherited.
Keep protection even when a compiler or renderer refuses it. Read
compliance and purposes for ESM v13, binder-only refusals,
consumer ceilings, marker repairs, reasons, scopes and provider limits.
What ships with it
18 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.
- LICENSE 142 B
- references/compliance.md 13 KB
- references/constraints-produces-concurrency.md 4.7 KB
- references/context.md 9.7 KB
- references/date-comparisons.md 5.7 KB
- references/described-handlers.md 4.6 KB
- references/enum-numbers.md 4.3 KB
- references/generated-values-and-responses.md 20 KB
- references/inline-events.md 4.8 KB
- references/operations.md 3.5 KB
- references/policy-persona-seed.md 4.5 KB
- references/protected-reads.md 8.7 KB
- references/routes-and-external-operations.md 1.3 KB
- references/shop-generation.md 6.0 KB
- references/text-and-match-rules.md 7.3 KB
- references/uuid-equality.md 5.4 KB
- references/validate-rules.md 5.5 KB
- verification.json 7.3 KB
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.
- 2d ago Changed c394a201086b
- 3d ago Changed · +3 lines 1b8af5ffbc38
- 4d ago Changed · +14 lines 2829398d8f33
- 7d ago Changed · -87 lines 78136a037c38
- 8d ago Changed · -5 lines 5d8c27505d04
- 9d ago Changed 47d37d1cc121
- 10d ago Changed · +13 lines 65b4c15a7f69
- 12d ago Changed · -151 lines 52ef45e554a3
- 14d ago Changed · +78 lines 4891caa70cc4
- 17d ago First seen · 460 lines · 126 tokens per session scan A 86adbaae0bfc
cratis-screenplay-command-surface is a skill published in the GitHub repository Cratis/AI (4 stars, last pushed yesterday), licensed MIT. It adds 126 tokens to every session and 4,305 once invoked, about $0.0005 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-09-19.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…