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 review-all-gddsgit 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/review-all-gdds)<a href="https://agentmods.dev/skills/donchitos/claude-code-game-studios/review-all-gdds"><img src="https://agentmods.dev/badge/skills/donchitos/claude-code-game-studios/review-all-gdds.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, 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 454 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- 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.00073 | $0.06346 |
| Opus 5 | $0.00036 | $0.03173 |
| Sonnet 5 | $0.00015 | $0.01269 |
| Haiku 4.5 | $0.00007 | $0.00635 |
Grade A, and why
review-all-gdds 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 4d 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:
- review-all-gdds — 100% identical, 3 lines differ
- review-all-gdds — 91% identical, 13 lines differ
- review-all-gdds — 88% identical, 25 lines differ
How it starts
The opening of the file, as written. The whole thing — 640 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review All GDDs
This skill reads every system GDD simultaneously and performs two complementary reviews that cannot be done per-GDD in isolation:
- Cross-GDD Consistency — contradictions, stale references, and ownership conflicts between documents
- Game Design Holism — issues that only emerge when you see all systems together: dominant strategies, broken economies, cognitive overload, pillar drift, competing progression loops
This is distinct from /design-review, which reviews one GDD for internal
completeness. This skill reviews the relationships between all GDDs.
When to run:
- After all MVP-tier GDDs are individually approved
- After any GDD is significantly revised mid-production
- Before
/create-architecturebegins (architecture built on inconsistent GDDs inherits those inconsistencies)
Argument modes:
Focus: $ARGUMENTS[0] (blank = full)
- No argument /
full: Both consistency and design theory passes consistency: Cross-GDD consistency checks only (faster)design-theory: Game design holism checks onlysince-last-review: Only GDDs modified since the last review report (git-based)
Phase 1: Load Everything
Phase 1a — L0: Summary Scan (fast, low tokens)
Before reading any full document, use Grep to extract ## Summary sections
from all GDD files:
Grep pattern="## Summary" glob="design/gdd/*.md" output_mode="content" -A 5
Display a manifest to the user:
Found [N] GDDs. Summaries:
• combat.md — [summary text]
• inventory.md — [summary text]
...
For since-last-review mode: run git log --name-only to identify GDDs
modified since the last review report file was written. Show the user which
GDDs are in scope based on summaries before doing any full reads. Only
proceed to L1 for those GDDs plus any GDDs listed in their "Key deps".
Phase 1b — Registry Pre-Load (fast baseline)
Before full-reading any GDD, check for the entity registry:
Read path="design/registry/entities.yaml"
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.
- 4d ago First seen · 640 lines · 73 tokens per session scan A 016dce629603
review-all-gdds is a skill published in the GitHub repository Donchitos/Claude-Code-Game-Studios (24,852 stars, last pushed 3mo ago), licensed MIT. It adds 73 tokens to every session and 6,346 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
media-higgsfield-assets
A Higgsfield workflow for creating or processing media beyond ordinary image and video generation. It covers 3D GLB models, rigging and animation, audio, video analysis, upscaling, reframing, outpainting, and background removal.
game-concept-architect
A structured method for turning a one-sentence game idea into a testable design plan, covering player actions, the core loop, scope, assumptions, and validation.
achievements
Steam-style achievement system with XP, levels, streaks, and skill trees. Gamifies the development workflow. 25 achievements across 5 categories.
unity-ecs
Use when considering ECS/DOTS architecture — when to use ECS vs MonoBehaviour, Burst compiler, Job System, hybrid approaches, and migration strategies from MonoBehaviour to ECS.
prefab-architecture
Use when designing prefab structure — base prefabs vs variants, nested prefabs, override strategies, prefab editing workflows, and when to use prefab variants vs ScriptableObject configs.
scene-architecture
Use when designing scene structure — single vs additive loading, bootstrap patterns, scene transitions, persistent managers, DontDestroyOnLoad decisions, and streaming world setups.