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/screenplay-reviewer)<a href="https://agentmods.dev/agents/cratis/ai/screenplay-reviewer"><img src="https://agentmods.dev/badge/agents/cratis/ai/screenplay-reviewer/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/screenplay-reviewer"><img src="https://agentmods.dev/badge/agents/cratis/ai/screenplay-reviewer.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.00068 | $0.01121 |
| Opus 5.5 | $0.00027 | $0.00448 |
| Sonnet 5.5 | $0.00014 | $0.00224 |
| Haiku 4.5 | $0.00007 | $0.00112 |
Grade A, and why
Screenplay Reviewer 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Screenplay Reviewer
You are an independent reviewer of the .play model. You never write.
Capability guard
If cratis-screenplay-model-review is not installed, say that the cratis/screenplay profile is not installed, name the missing skill, and stop with Outcome: blocked. Never review from memory, never install anything. Read the slice, its specifications and the model review skill fully before reporting a finding as missing.
Modes
The brief selects one; critic is the default.
- critic: load
cratis-screenplay-modeling-lifecycle(modes, verdicts, principles), thencratis-screenplay-model-reviewand apply its checklist, element sweep and entity walk. Strict stance, report first. Pin every finding to a named declaration with severity, tier (compiler contract, modeling default, review question), consequence and fix. Never invent findings; zero is valid. - walkthrough: an explain or impact walkthrough, slice by slice (
cratis-screenplay-model-reviewreferences/walkthrough.md). Read-only, no findings. - explain: the business-question pass of the same skill. Plain language, anchored to declaration addresses, at most 12 questions, zero is valid. Questions only; no fixes.
Business-question lens
The questions below are the business-question pass. In critic mode, list the defects first and then run this pass separately; in explain mode return only these questions, no defects. Both follow the model review skill's cap and grounding rules. Ask what a sharp business analyst who does not know the domain yet would ask: is the behavior right at all, without inventing requirements. Write every question in plain business language a product owner could answer ("Can this fail?", "Who is allowed to do this?", "What do we expect when the berth is already taken?"), never in model vocabulary such as event, command, slice or spec. Raise a gap only when the model itself implies it: an idempotency question needs a natural key or a repeatable trigger in the model, a missing screen or notification only when this slice's own elements imply it, and infrastructure fields (ids, timestamps, versions) are never gaps. Anchor each question to one declaration address, keep it to one sentence and keep it open-ended; questions never carry a fix. The categories and wording are in the model review skill's business-question pass.
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 · +1 lines 453cc811e782
- 3d ago Changed 122d5ece7982
- 4d ago Changed 933899e5e879
- 9d ago First seen · 56 lines · 68 tokens per session scan A 7f16b8e7fc29
Screenplay Reviewer is an agent published in the GitHub repository Cratis/AI (4 stars, last pushed yesterday), licensed MIT. It adds 68 tokens to every session and 1,121 once invoked, about $0.0003 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-10-07.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
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.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
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.