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 agentmods add skills/donchitos/claude-code-game-studios/retrospectivenpx skills add Donchitos/Claude-Code-Game-Studios --skill retrospectivegit 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/retrospective)<a href="https://agentmods.dev/skills/donchitos/claude-code-game-studios/retrospective"><img src="https://agentmods.dev/badge/skills/donchitos/claude-code-game-studios/retrospective.svg" alt="Measured on agentmods" 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.00032 | $0.02158 |
| Opus 5 | $0.00016 | $0.01079 |
| Sonnet 5 | $0.00006 | $0.00432 |
| Haiku 4.5 | $0.00003 | $0.00216 |
Grade A, and why
retrospective 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.
Copies of this mod
3 near-identical copies found in the catalogue:
- retrospective — 100% identical, 1 lines differ
- retrospective — 86% identical, 47 lines differ
- retrospective — 81% identical, 49 lines differ
How it starts
The opening of the file, as written. The whole thing — 222 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Phase 1: Parse Arguments
Determine whether this is a sprint retrospective (sprint-N) or a milestone retrospective (milestone-name).
Phase 1b: Check for Existing Retrospective
Before loading any data, glob for an existing retrospective file:
- For sprint retrospectives:
production/retrospectives/retro-[sprint-slug]-*.md(also checkproduction/sprints/sprint-[N]-retrospective.mdas an alternate location) - For milestone retrospectives:
production/retrospectives/retro-[milestone-name]-*.md
If a matching file is found, use AskUserQuestion:
- Prompt: "An existing retrospective was found: [filename]. How do you want to proceed?"
- Options:
[A] Update existing — load it and add/revise sections with new data[B] Start fresh — generate a new retrospective (archive the old one)
If [A]: read the existing file and carry its content forward, revising sections with new data.
If [B]: continue to Phase 2 with a blank slate. Before writing the new file, rename the existing one with a -archived-[date] suffix.
Phase 2: Load Sprint or Milestone Data
Read the sprint or milestone plan from the appropriate location:
- Sprint plans:
production/sprints/ - Milestone definitions:
production/milestones/
Also check for production/sprint-status.yaml: if it exists, read it alongside the sprint plan. It is the authoritative source for actual story completion status (status: done, completed dates, blockers). Use it as the primary source for completion metrics in Phase 3. Fall back to markdown scanning only if the yaml does not exist. Note discrepancies between the yaml and the sprint plan (e.g., stories in yaml not in plan, or vice versa).
If the file does not exist or is empty, output:
"No sprint data found for [sprint/milestone]. Run
/sprint-statusto generate sprint data first, or provide the sprint details manually."
Then use AskUserQuestion to present two options:
- [A] Provide data manually — ask the user to paste or describe the sprint tasks, dates, and outcomes; use that as the source of truth for the retrospective.
- [B] Stop — abort the skill. Verdict: BLOCKED — no sprint data available.
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 First seen · 222 lines · 32 tokens per session scan A 60f9525887c9
retrospective is a skill published in the GitHub repository Donchitos/Claude-Code-Game-Studios (24,822 stars, last pushed 3mo ago), licensed MIT. It adds 32 tokens to every session and 2,158 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-09-03.
Other skills, from other repositories
security-audit
Java security checklist covering OWASP Top 10, input validation, injection prevention, and secure coding. Works with Spring, Quarkus, Jakarta EE, and plain Java. Use when reviewing code security, before releases, or when user asks about vulnerabilities.
solid-principles
SOLID principles checklist with Java examples. Use when a class has too many responsibilities, an abstraction leaks, or a dependency points the wrong way, and when the user asks about Single Responsibility, Open/Closed, Liskov, Interface Segregation or Dependency Inversion. For naming, duplication and method length…
issue-triage
Triage and categorize GitHub issues with priority labels. Use when user says "triage issues", "check issues", "review open issues", or during regular maintenance of GitHub issue backlog.
engineering-wisdom
Provide an explicitly requested, repository-grounded engineering review using contextual heuristics for code clarity, SOLID and design, testing, refactoring, architecture, and professional practice. Use only when the user invokes $engineering-wisdom or explicitly asks for this installed engineering-wisdom pack; do not…
novel-game-analyze
Deconstruct a novel for game adaptation. Compress a raw novel, deconstruction library, or writing project into a SOURCEBIBLE with cited textual evidence, extracting world rules, player verbs, spaces, character will, systems, and visual anchors — without inventing a genre yet. Use for gameable book analysis, analyze a…
game-design
Use when designing or repairing what makes a game fun — verbs and mechanics, moment-to-moment/session/meta loops, progression, economy faucets and sinks, difficulty curves, dominant strategies, juice, prototyping and scope. NOT engine code (that is godot), NOT story (that is game-storytelling), NOT level layout (that…