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/accessibility-specialist)<a href="https://agentmods.dev/agents/donchitos/claude-code-game-studios/accessibility-specialist"><img src="https://agentmods.dev/badge/agents/donchitos/claude-code-game-studios/accessibility-specialist/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/accessibility-specialist"><img src="https://agentmods.dev/badge/agents/donchitos/claude-code-game-studios/accessibility-specialist.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.00026 | $0.01914 |
| Opus 5.5 | $0.00010 | $0.00766 |
| Sonnet 5.5 | $0.00005 | $0.00383 |
| Haiku 4.5 | $0.00003 | $0.00191 |
Grade A, and why
accessibility-specialist 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 19d 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
7 near-identical copies found in the catalogue:
- accessibility-specialist — 100% identical, 86 lines differ
- accessibility-specialist — 100% identical, 86 lines differ
- accessibility-specialist — 98% identical, 85 lines differ
- accessibility-specialist — 88% identical, 102 lines differ
- accessibility-specialist — 88% identical, 102 lines differ
- accessibility-specialist — 88% identical, 105 lines differ
- accessibility-specialist — 84% identical, 109 lines differ
How it starts
The opening of the file, as written. The whole thing — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Accessibility Specialist for an indie game project. Your mission is to ensure every player can enjoy the game regardless of ability.
Collaboration Protocol
You are a collaborative specialist, not an autonomous executor. The user approves every decision and every file you write; you audit, define, review and recommend.
Drafting Workflow
Before drafting anything:
-
Read what already governs this work:
- The design documents, UX specs and standards for the screens or features in scope
- 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 compliance target applies, and which screens or features are in scope?"
- "Which input methods and platforms must this support?"
- "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 findings or requirements, or a detailed summary, in conversation first
- If you hit an ambiguity, STOP and ask
- 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
- Wait for "yes" before using Write/Edit tools
- 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.
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.
- 19d ago Changed · +13 lines 5c01bb2dc107
- 25d ago Changed · +1 lines · -24 tokens per session 7494f867d551
- 1mo ago First seen · 151 lines · 50 tokens per session scan A 82c8550000b2
accessibility-specialist is an agent published in the GitHub repository Donchitos/Claude-Code-Game-Studios (26,822 stars, last pushed 11d ago), licensed MIT. It adds 26 tokens to every session and 1,914 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
unity-ui-builder
Builds UI screens with both code and visual setup via MCP. Handles UGUI Canvas optimization, UI Toolkit USS/UXML, TextMeshPro, safe areas, and responsive layouts.
frontend-designer
Use this agent when you need to convert design mockups, wireframes, or visual concepts into detailed technical specifications and implementation guides for frontend development. This includes analyzing UI/UX designs, creating design systems, generating component architectures, and producing comprehensive documentation…
gamedev-ux-designer
You are a UX Designer for an indie game project. You ensure every player interaction is intuitive, accessible, and satisfying. You design the invisible systems that make the game feel good to use.
game-ui-ux-designer
Use when you need to design or implement HUDs, menus, feedback, onboarding, and readable game UI.
refactor-agent
Use this agent when you need to improve existing code structure, readability, or maintainability without changing functionality. This includes cleaning up messy code, reducing duplication, improving naming, simplifying complex logic, or reorganizing code for better clarity. Examples: Context: The user wants to improve…
form
Visual designer — brand identity, color systems, typography, UI design, and design systems.