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 milestone-reviewgit 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/milestone-review)<a href="https://agentmods.dev/skills/donchitos/claude-code-game-studios/milestone-review"><img src="https://agentmods.dev/badge/skills/donchitos/claude-code-game-studios/milestone-review.svg" alt="Measured on agentmods" 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.00040 | $0.01318 |
| Opus 5 | $0.00020 | $0.00659 |
| Sonnet 5 | $0.00008 | $0.00264 |
| Haiku 4.5 | $0.00004 | $0.00132 |
Grade A, and why
milestone-review 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:
- milestone-review — 92% identical, 5 lines differ
How it starts
The opening of the file, as written. The whole thing — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Phase 0: Parse Arguments
Extract the milestone name (current or a specific name) and resolve the review mode (once, store for all gate spawns this run):
- If
--review [full|lean|solo]was passed → use that - Else read
production/review-mode.txt→ use that value - Else → default to
lean
See .claude/docs/director-gates.md for the full check pattern.
Phase 1: Load Milestone Data
Read the milestone definition from production/milestones/. If the argument is current, use the most recently modified milestone file.
Read all sprint reports for sprints within this milestone from production/sprints/.
Phase 2: Scan Codebase Health
- Scan for
TODO,FIXME,HACKmarkers that indicate incomplete work - Check the risk register at
production/risk-register/
Phase 3: Generate the Milestone Review
# Milestone Review: [Milestone Name]
## Overview
- **Target Date**: [Date]
- **Current Date**: [Today]
- **Days Remaining**: [N]
- **Sprints Completed**: [X/Y]
## Feature Completeness
### Fully Complete
| Feature | Acceptance Criteria | Test Status |
|---------|-------------------|-------------|
### Partially Complete
| Feature | % Done | Remaining Work | Risk to Milestone |
|---------|--------|---------------|------------------|
### Not Started
| Feature | Priority | Can Cut? | Impact of Cutting |
|---------|----------|----------|------------------|
## Quality Metrics
- **Open S1 Bugs**: [N] -- [List]
- **Open S2 Bugs**: [N]
- **Open S3 Bugs**: [N]
- **Test Coverage**: [X%]
- **Performance**: [Within budget? Details]
## Code Health
- **TODO count**: [N across codebase]
- **FIXME count**: [N]
- **HACK count**: [N]
- **Technical debt items**: [List critical ones]
## Risk Assessment
| Risk | Status | Impact if Realized | Mitigation Status |
|------|--------|-------------------|------------------|
## Velocity Analysis
- **Planned vs Completed** (across all sprints): [X/Y tasks = Z%]
- **Trend**: [Improving / Stable / Declining]
- **Adjusted estimate for remaining work**: [Days needed at current velocity]
## Scope Recommendations
### Protect (Must ship with milestone)
- [Feature and why]
### At Risk (May need to cut or simplify)
- [Feature and risk]
### Cut Candidates (Can defer without compromising milestone)
- [Feature and impact of cutting]
## Go/No-Go Assessment
**Recommendation**: [GO / CONDITIONAL GO / NO-GO]
**Conditions** (if conditional):
- [Condition 1 that must be met]
- [Condition 2 that must be met]
**Rationale**: [Explanation of the recommendation]
## Action Items
| # | Action | Owner | Deadline |
|---|--------|-------|----------|
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 · 157 lines · 40 tokens per session scan A 736a1cffb028
milestone-review is a skill published in the GitHub repository Donchitos/Claude-Code-Game-Studios (24,880 stars, last pushed 3mo ago), licensed MIT. It adds 40 tokens to every session and 1,318 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
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.
game-producer
Invoke when the user asks about sprint planning, milestone tracking, scope management, risk assessment, scheduling, resource allocation, team velocity, or needs production coordination across the development team. Triggers on: "sprint", "milestone", "scope", "risk", "schedule", "resource", "velocity", "deadline"…