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-qagit 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-qa)<a href="https://agentmods.dev/skills/donchitos/claude-code-game-studios/team-qa"><img src="https://agentmods.dev/badge/skills/donchitos/claude-code-game-studios/team-qa/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-qa"><img src="https://agentmods.dev/badge/skills/donchitos/claude-code-game-studios/team-qa.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.00035 | $0.06332 |
| Opus 5.5 | $0.00014 | $0.02533 |
| Sonnet 5.5 | $0.00007 | $0.01266 |
| Haiku 4.5 | $0.00003 | $0.00633 |
Grade A, and why
team-qa 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 11d 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.
How it starts
The opening of the file, as written. The whole thing — 388 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Team QA
When this skill is invoked, orchestrate the QA team through a structured testing cycle.
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,qa.level
Resolved above — use as-is; --review overrides review_mode. No block →
defaults in .claude/docs/config-resolution.md.
qa.level decides what a Logic, Integration or Config/Data story's evidence is:
its automated test at standard and full; at minimal, where tests are waived
(.claude/docs/coding-standards.md), the acceptance-criteria walk in Phase 5 —
a story without a test is then WAIVED, not missing its evidence. The UI and
Visual/Feel screenshots are required at every level.
review_mode sets director-gate depth, and this pipeline has no director gate:
no phase below spawns CD-, TD-, PR- or AD-PHASE-GATE, at any review_mode. Its
phase gates are the pipeline's own decision points (defined under team.size
below), and the agents that work at them are team members, not director gates.
automation drives the Decision Points note above. See the Decision Points note above and
.claude/docs/automation-modes.md for how each mode changes pipeline behavior.
team.size: which agents are active (orthogonal to review_mode gate-depth and workflow docs).
individual(default):qa-testeronly;qa-leadinvoked at phase gates only.small:qa-lead+qa-testerpipeline (as documented).studio:qa-lead+ per-storyqa-testerspawn + sign-off. A non-core agent needed atindividualroutes through the nearest active core agent with an informational note. "Phase gate" means any phase that ends in anAskUserQuestiondecision point this pipeline itself lists — a transition under Decision Points above, or a Gate step written into the pipeline below — whatever theautomationmode: inguidedorautonomous, where that question is skipped or logged, the phase is still a gate. Not every phase is one. Apply the test literally: if the phase below lists no decision point, it is not a gate, and an agent restricted to "phase gates only" is not spawned for it. This active-set scoping applies throughout the pipeline below: any phase that names an agent outside the active set routes through the nearest core agent rather than spawning it.
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.
- 11d ago Changed · +2 lines 19448b889561
- 20d ago Changed · +44 lines 0ab2bc67d3a9
- 25d ago Changed 9aa3c2cca046
- 26d ago Changed · +97 lines · -38 tokens per session 98e82cea35b3
- 1mo ago First seen · 245 lines · 73 tokens per session scan A 1d67b5e45ae4
team-qa is a skill published in the GitHub repository Donchitos/Claude-Code-Game-Studios (26,893 stars, last pushed yesterday), licensed MIT. It adds 35 tokens to every session and 6,332 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
autonomous-dev
Drives a brief, specification, issue or existing PR through implementation, review, tests and QA to a ready PR. Persists ownership, progress and commit-bound evidence for safe resumption. Use for autonomous software delivery or finishing an interrupted development run.
implementation-phase
Executes implementation tasks using Test-Driven Development, prevents code duplication through anti-duplication checks, and maintains quality through continuous testing. Use when implementing features from tasks.md, during the /implement phase, or when the user requests TDD-based implementation. (project).
nightly-close-parity
Unique project-local fire verb for the seven-leg nightly close-parity pass. Proves and loads the canonical top-level skill.
build-evaluate
Verify a completed build against the PRD's anchor case and success criteria. Runs the acceptance test and anchor-case check (serial across drivers sharing a write root), fans out 2-3 read-only cold-read agents (fresh-eyes, anti-scope-creep, drift-vs-mirror). On FAIL, auto-invokes five-whys for root-cause. On PASS with…
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.
evidence-publish
Deliver a QA/evidence packet to a tracker or keep it local, behind an always-ask preview gate. Protocol for /orc:qa Phase 6, /orc:evidence, and any evidence-delivery step.