Claude Code Game Studios is a setup that organizes Claude Code into a coordinated game-development team of specialized AI agents. It supports game projects across design, programming, art, audio, narrative, quality assurance, and production, with skills and workflows for coordinating that work.
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 Donchitos/Claude-Code-Game-Studios --skill story-readinessgit clone --depth 1 https://github.com/Donchitos/Claude-Code-Game-StudiosWrote 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/donchitos/claude-code-game-studios/story-readiness)<a href="https://agentmods.dev/skills/donchitos/claude-code-game-studios/story-readiness"><img src="https://agentmods.dev/badge/skills/donchitos/claude-code-game-studios/story-readiness/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/donchitos/claude-code-game-studios/story-readiness"><img src="https://agentmods.dev/badge/skills/donchitos/claude-code-game-studios/story-readiness.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 7 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
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.00077 | $0.03859 |
| Opus 5 | $0.00039 | $0.01929 |
| Sonnet 5 | $0.00015 | $0.00772 |
| Haiku 4.5 | $0.00008 | $0.00386 |
Grade A, and why
story-readiness 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
3 near-identical copies found in the catalogue:
- story-readiness — 95% identical, 5 lines differ
- story-readiness — 94% identical, 19 lines differ
- story-readiness — 92% identical, 44 lines differ
How it starts
The opening of the file, as written. The whole thing — 356 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Story Readiness
This skill validates that a story file contains everything a developer needs to begin implementation — no mid-sprint design interruptions, no guessing, no ambiguous acceptance criteria. Run it before assigning a story.
This skill is read-only. It never edits story files. It reports findings and asks whether the user wants help filling gaps.
Output: Verdict per story (READY / NEEDS WORK / BLOCKED) with a specific gap list for each non-ready story.
Phase 0: Resolve Review Mode
Resolve the review mode once at startup (store for all gate spawns this run):
- If skill was called with
--review [full|lean|solo]→ use that value - Else read
production/review-mode.txt→ use that value - Else → default to
lean
See .claude/docs/director-gates.md for the full check pattern and mode definitions.
1. Parse Arguments
Scope: $ARGUMENTS[0] (blank = ask user via AskUserQuestion)
- Specific path (e.g.,
/story-readiness production/epics/combat/story-001-basic-attack.md): validate that single story file. sprint: read the current sprint plan fromproduction/sprints/(most recent file), extract every story path it references, validate each one.all: globproduction/epics/**/*.md, excludeEPIC.mdindex files, validate every story file found.- No argument: ask the user which scope to validate.
If no argument is given, use AskUserQuestion:
- "What would you like to validate?"
- Options: "A specific story file", "All stories in the current sprint", "All stories in production/epics/", "Stories for a specific epic"
Report the scope before proceeding: "Validating [N] story files."
2. Load Supporting Context
Before checking any stories, load reference documents once (not per-story):
design/gdd/systems-index.md— to know which systems have approved GDDsdocs/architecture/control-manifest.md— to know which manifest rules exist (if the file does not exist, note it as missing once; do not re-flag per story) Also extract theManifest Version:date from the header block if the file exists.docs/architecture/tr-registry.yaml— index all entries byid. Used to validate TR-IDs in stories. If the file does not exist, note it once; TR-ID checks will auto-pass for all stories (registry predates stories, so missing registry means stories are from before TR tracking was introduced).- All ADR status fields — for each unique ADR referenced across the stories being
checked, read the ADR file and note its
Status:field. Cache these so you don't re-read the same ADR for every story. - The current sprint file (if scope is
sprint) — to identify Must Have / Should Have priority for escalation decisions
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 First seen · 356 lines · 77 tokens per session scan A f1fc25f80f81
story-readiness is a skill published in the GitHub repository Donchitos/Claude-Code-Game-Studios (24,880 stars, last pushed 3mo ago), licensed MIT. It adds 77 tokens to every session and 3,859 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
spec-driven-dev
A guide for planning software changes in specification documents before implementation. Spec-Driven Development means proposing, reviewing, implementing, verifying, and archiving a change in defined stages.
requirement-assistant
A guide for writing clear requirements, user stories, and feature specifications. A user story describes a need from a user's point of view and the reason it matters.
dare-refine
Analisa complexidade de uma task DARE e, quando alta, quebra em sub-tasks menores. Use após gerar o DAG (para tasks HIGH/CRITICAL), quando o dev pedir refinamento manual, ou quando o escopo mudou e uma task ficou grande. Combina heurística determinística (CLI) com decisão semântica do agente.
dare-graph
Consulta e visualiza o grafo de conhecimento do projeto (tasks, arquivos, schemas, endpoints, componentes, entidades e suas relações). Mapeia o CLI dare graph.
dare-dag
Mostra o DAG estático de tasks (DARE/dare-dag.yaml): ranks, dependências e caminho crítico. Use dare dag viz para exportar o diagrama. Mapeia o CLI dare dag.
project-diagnosis
Structured gap analysis that identifies what a project is missing — not what's done poorly (that's /audit), but what's absent entirely. Checks for tests, CI, security basics, linting, type safety, deployment readiness, and dependency health. Each finding has a severity and a concrete fix action.