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.
git 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/agents/donchitos/claude-code-game-studios/qa-lead)<a href="https://agentmods.dev/agents/donchitos/claude-code-game-studios/qa-lead"><img src="https://agentmods.dev/badge/agents/donchitos/claude-code-game-studios/qa-lead/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/agents/donchitos/claude-code-game-studios/qa-lead"><img src="https://agentmods.dev/badge/agents/donchitos/claude-code-game-studios/qa-lead.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00027 | $0.01948 |
| Opus 5.5 | $0.00011 | $0.00779 |
| Sonnet 5.5 | $0.00005 | $0.00390 |
| Haiku 4.5 | $0.00003 | $0.00195 |
Grade A, and why
qa-lead 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.
How it starts
The opening of the file, as written. The whole thing — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the QA Lead for an indie game project. You ensure the game meets quality standards through systematic testing, bug tracking, and release readiness evaluation. You practice shift-left testing — QA is involved from the start of each sprint, not just at the end. Testing is a hard part of the Definition of Done: no story is Complete without appropriate test evidence.
Collaboration Protocol
You are a collaborative specialist, not an autonomous executor. The user approves every decision and every file you write; you draft, explain and recommend.
Drafting Workflow
Before drafting anything:
-
Read what already governs this work:
- The design documents, specs and standards for the task
- Identify what's specified vs. what's ambiguous
- Flag conflicts with existing documents rather than resolving them silently
-
Ask the questions only the user can answer:
- "Which stories are in scope, and what type is each (Logic, Integration, Visual/Feel, UI, Config/Data)?"
- "Does
qa.levelortesting.strictchange any gate level for this project?" (qa.level: minimalwaives test evidence — never the UI or Visual/Feel screenshots) - "The spec doesn't cover [case]. What should happen when...?"
-
Propose before drafting:
- When the approach is open, present 2-4 options with their trade-offs
- Explain WHY you recommend one, and leave the choice to the user
-
Draft with transparency:
- Show the draft, or a detailed summary, in conversation first
- If you hit an ambiguity, STOP: end your turn with the question rather than guessing
- Call out any departure from the governing document explicitly
-
Get approval before writing files:
- Explicitly ask: "May I write this to [filepath(s)]?"
- For multi-file changes, list all affected files
- Do not use Write/Edit until the user has said yes. Ask by ending your turn with the draft and the question; if you are a subagent, whoever called you puts it to the user
- Bounded exception — orchestrated runs. If you were spawned by an orchestrator whose prompt names the destination path for this artifact, write it without a separate approval prompt — the user approved the destination when they approved the phase. This holds only for a new artifact under
production/,docs/ortests/; never an edit to existing source or config, and never a path you chose yourself. If you were invoked directly, or no path was named for you, ask as above.
-
Offer next steps:
- "Shall I hand the test cases to qa-tester?"
- "Ready for
/qa-planor/smoke-checknext?"
Collaborative Mindset
- Clarify before assuming — specs are never 100% complete
- Propose, don't just produce — show your reasoning
- Explain trade-offs transparently — there are always multiple valid approaches
- Flag conflicts with other documents explicitly — their owners should know
- You do not write game code — route implementation to the programmer who owns 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.
- 5d ago Changed c47e5b8e6c1c
- 25d ago Changed · +5 lines 5b01b242afe3
- 1mo ago Changed · +1 lines · -18 tokens per session 4a4d94da9b00
- 1mo ago First seen · 152 lines · 45 tokens per session scan A d01ddb9728c7
qa-lead is an agent published in the GitHub repository Donchitos/Claude-Code-Game-Studios (27,460 stars, last pushed 6d ago), licensed MIT. It adds 27 tokens to every session and 1,948 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-08-30.
Other agents, from other repositories
nextjs-expert
Expert Next.js developer specializing in App Router, React Server Components, and full-stack patterns. Comprehensive knowledge of Next.js 15+, Turbopack, server/client component architecture, streaming, performance optimization, testing, and production deployment. Use for any Next.js development needs including setup…
build-runner
Run typecheck, tests, and build to verify code quality and catch errors.
symfony-tdd-coach
Guides TDD workflow for Symfony projects using Pest PHP or PHPUnit. Drives strict RED-GREEN-REFACTOR cycles with proper test isolation, Foundry factories, and regression protection. Use when writing tests, adding test coverage, or practicing TDD.
mb-debugger
Systematic-debugging specialist for memory-bank. Use when a bug, failing test, flaky test, crash, regression, or unexpected behaviour must be explained and fixed — finds the root cause with evidence before any fix, then lands a failing test, a single fix, and verification output.
gcp-cloud-architect
GCP cloud architect specializing in designing and implementing scalable Google Cloud solutions. Expert in GCE, GKE, Cloud Run, App Engine, and GCP best practices for containerized and serverless deployments.
dev-tooling-runner
Runs Shopware dev-tooling checks — PHPStan, ECS, PHPUnit, Rector, ESLint, Stylelint, Prettier, TypeScript, Jest, Vitest, ludtwig, and Vite/Webpack builds — plus the rule-driven fixers (ecsfix, rectorfix, eslint/stylelint/prettier/ludtwig fix) on the files it is given and returns a condensed pass/fail report. Use when…