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 team-releasegit 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/team-release)<a href="https://agentmods.dev/skills/donchitos/claude-code-game-studios/team-release"><img src="https://agentmods.dev/badge/skills/donchitos/claude-code-game-studios/team-release/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/team-release"><img src="https://agentmods.dev/badge/skills/donchitos/claude-code-game-studios/team-release.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.00033 | $0.05181 |
| Opus 5.5 | $0.00013 | $0.02072 |
| Sonnet 5.5 | $0.00007 | $0.01036 |
| Haiku 4.5 | $0.00003 | $0.00518 |
Grade A, and why
team-release 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 today.
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
4 near-identical copies found in the catalogue:
- team-release — 98% identical, 227 lines differ
- team-release — 89% identical, 240 lines differ
- team-release — 88% identical, 247 lines differ
- team-release — 86% identical, 232 lines differ
How it starts
The opening of the file, as written. The whole thing — 305 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Team Release
Argument check: If no version number is provided:
- Read
production/session-state/active.mdand the most recent file inproduction/milestones/(if they exist) to infer the target version. - If a version is found: report "No version argument provided — inferred [version] from milestone data. Proceeding." Then confirm with
AskUserQuestion: "Releasing [version]. Is this correct?" - If no version is discoverable: use
AskUserQuestionto ask "What version number should be released? (e.g., v1.0.0)" and wait for user input before proceeding. Do NOT default to a hardcoded version string.
When this skill is invoked, orchestrate the release team through a structured pipeline.
Decision Points: At each phase transition, use AskUserQuestion to present
the user with the subagent's proposals as selectable options. Write the agent's
full analysis in conversation, then capture the decision with concise labels.
In collaborative mode, the user must approve before moving to the next phase.
In guided mode the pipeline advances automatically unless a phase is BLOCKED;
in autonomous mode it runs end to end, recording each phase outcome via
log_decision. Decisions in automation_always_ask categories
(is_always_ask_category helper) always prompt regardless of mode. See
.claude/docs/automation-modes.md.
Phase 0: Resolve Config
!bash "${CLAUDE_SKILL_DIR}/../../hooks/yaml-helper.sh" resolve_config --keys review_mode,automation,team.size,workflow,project.stage
Resolved above — use as-is; --review overrides review_mode. No block →
defaults in .claude/docs/config-resolution.md.
Stage check — before anything is spawned. This skill ships a release, and
/gate-check release is the readiness gate that must pass first; only its PASS
sets project.stage to Release. If the resolved project.stage is anything
else — Polish, an earlier stage, or not set — stop before Phase 1 and spawn
nothing:
"The release readiness gate has not passed (project.stage: [stage]) — run
/gate-check releasefirst."
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.
- today Changed 7b9950f0848a
- 11d ago Changed · +2 lines 701926468649
- 20d ago Changed · +44 lines d7fbdf2807a2
- 25d ago Changed c1c2c15da223
- 26d ago Changed · +90 lines · -1 tokens per session ade805671f14
- 1mo ago First seen · 169 lines · 34 tokens per session scan A 9cb0f1c15b4a
team-release is a skill published in the GitHub repository Donchitos/Claude-Code-Game-Studios (26,893 stars, last pushed yesterday), licensed MIT. It adds 33 tokens to every session and 5,181 once invoked, about $0.0001 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
batch
Research and plan a large-scale change, then execute it in parallel across 5–30 isolated worktree agents that each open a PR.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
close-task-commit-push-pr
Close the active backlog task (detected from branch name), commit all changes, push to remote, and open a pull request. Use when the user says "close task and ship it", "close task commit push pr", or invokes /close-task-commit-push-pr.
github-project-management
GitHub project management with issue tracking, project-board automation, and sprint planning. Use when triaging or organizing issues, automating a project board, planning a sprint, or running release/roadmap coordination on GitHub.
gh-cli
GitHub CLI (gh) reference for repos, issues, PRs, Actions, releases, gists, projects, codespaces, and the API. Use for any gh command or GitHub operation from the terminal.
push-updates
CEO-only: Publish workspace updates for all executives. Single command that commits the engine clone and the data overlay, classifies, publishes corporate-routed content to the corporate repo, bumps BUILD.json, pushes both repos through scripts/push-all.py, refreshes the operator's own CRM aggregate, and reports. Each…