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
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/Donchitos/Claude-Code-Game-Studiosnpx agentmods add skills/donchitos/claude-code-game-studios/create-epicsWrote 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/create-epics)<a href="https://agentmods.dev/skills/donchitos/claude-code-game-studios/create-epics"><img src="https://agentmods.dev/badge/skills/donchitos/claude-code-game-studios/create-epics/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/create-epics"><img src="https://agentmods.dev/badge/skills/donchitos/claude-code-game-studios/create-epics.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.00049 | $0.03250 |
| Opus 5.5 | $0.00020 | $0.01300 |
| Sonnet 5.5 | $0.00010 | $0.00650 |
| Haiku 4.5 | $0.00005 | $0.00325 |
Grade A, and why
create-epics 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 6d 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:
- create-epics — 92% identical, 333 lines differ
- create-epics — 91% identical, 316 lines differ
- create-epics — 86% identical, 316 lines differ
How it starts
The opening of the file, as written. The whole thing — 268 lines — stays where its author put it; the contents beside it link to each section on GitHub.
!bash "${CLAUDE_SKILL_DIR}/../../hooks/yaml-helper.sh" resolve_config --keys review_mode,review_gate,automation,workflow,docs.density,engine_values,system_overrides
Resolved above — use as-is; --review overrides review_mode. No block →
defaults in .claude/docs/config-resolution.md.
Ask with the question tool. Without one, list the options numbered and end your turn to wait. A skipped or dismissed question is not an answer: ask again in plain text.
Create Epics
An epic is a bounded body of work for one architectural module: what gets built and which decisions govern it. How to build it is for the stories. Run it once per layer as development reaches that layer: Feature epics written before Core is nearly done describe a design that will have changed.
Writes: production/epics/[epic-slug]/EPIC.md per epic and its row in
production/epics/index.md, each after its own yes.
Next: /create-stories [epic-slug] per epic. This skill never writes a story.
Asks follow .claude/docs/automation-modes.md (collaborative always asks, guided
asks on major choices, autonomous logs and goes on; automation_always_ask
categories always ask).
Checklist (copy it and tick as you go):
- [ ] Phase 1: scope and tier
- [ ] Phase 2: inputs loaded and reported
- [ ] Phase 3: each epic shown, "Shall I create Epic: …?" asked one at a time
- [ ] Phase 4: producer review run, or its skip noted
- [ ] Phase 5: each EPIC.md and index row written after its own yes
- [ ] Phase 6: closing block printed
Phase 1: Scope and tier
The text typed after the skill name, with any --review <mode> pair removed:
all: every system, in layer order.layer: foundation(orcore,feature,presentation): that layer only.- a system name: that system only.
- nothing: the request's own words when they name a layer or system ("foundation and core"); else ask "Which layer or system would you like epics for?"
Tier. The project's workflow value sets what is required (Phase 2). Each
in-scope system's own GDD bar comes from its system_overrides row, when it has one.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 6d ago Changed · -102 lines · +12 tokens per session a867fed460ac
- 26d ago Changed · +26 lines 7a4d61c61be7
- 1mo ago Changed 71a7c37dad9a
- 1mo ago Changed · +98 lines · -24 tokens per session df989f678ee4
- 1mo ago First seen · 246 lines · 61 tokens per session scan A 5a761ad27214
create-epics is a skill published in the GitHub repository Donchitos/Claude-Code-Game-Studios (27,550 stars, last pushed 7d ago), licensed MIT. It adds 49 tokens to every session and 3,250 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
work-log-claude
A work-log generator that reads Claude Code's local session records and produces an evidence-based Markdown report. It can organise work by project and time period while excluding unrelated session data.
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.
tech-debt-tracking
Track shortcuts with justifications, prevent debt accumulation, and surface outstanding debt at session start.