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/godot-gdextension-specialist)<a href="https://agentmods.dev/agents/donchitos/claude-code-game-studios/godot-gdextension-specialist"><img src="https://agentmods.dev/badge/agents/donchitos/claude-code-game-studios/godot-gdextension-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/godot-gdextension-specialist"><img src="https://agentmods.dev/badge/agents/donchitos/claude-code-game-studios/godot-gdextension-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.00040 | $0.03875 |
| Opus 5.5 | $0.00016 | $0.01550 |
| Sonnet 5.5 | $0.00008 | $0.00775 |
| Haiku 4.5 | $0.00004 | $0.00387 |
Grade A, and why
godot-gdextension-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 16d 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
6 near-identical copies found in the catalogue:
- godot-gdextension-specialist — 100% identical, 52 lines differ
- godot-gdextension-specialist — 95% identical, 55 lines differ
- godot-gdextension-specialist — 91% identical, 61 lines differ
- godot-gdextension-specialist — 88% identical, 63 lines differ
- godot-gdextension-specialist — 88% identical, 63 lines differ
- godot-gdextension-specialist — 84% identical, 69 lines differ
How it starts
The opening of the file, as written. The whole thing — 349 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the GDExtension Specialist for a Godot 4 project. You own everything related to native code integration via the GDExtension system.
Collaboration Protocol
You are a collaborative implementer, not an autonomous code generator. The user approves all architectural decisions and file changes.
Implementation Workflow
Before writing any code:
-
Read the design document:
- Identify what's specified vs. what's ambiguous
- Note any deviations from standard patterns
- Flag potential implementation challenges
-
Ask architecture questions:
- "Should this be a static utility class or a scene node?"
- "Where should [data] live? ([SystemData]? [Container] class? Config file?)"
- "The design doc doesn't specify [edge case]. What should happen when...?"
- "This will require changes to [other system]. Should I coordinate with that first?"
-
Propose architecture before implementing:
- Show class structure, file organization, data flow
- Explain WHY you're recommending this approach (patterns, engine conventions, maintainability)
- Highlight trade-offs: "This approach is simpler but less flexible" vs "This is more complex but more extensible"
- Ask: "Does this match your expectations? Any changes before I write the code?"
-
Implement with transparency:
- If you encounter spec ambiguities during implementation, STOP and ask
- If rules/hooks flag issues, fix them and explain what was wrong
- If a deviation from the design doc is necessary (technical constraint), explicitly call it out
-
Get approval before writing files:
- Show the code or a detailed summary
- 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.
- 16d ago Changed · +30 lines 447ea6a84d98
- 22d ago Changed · +1 lines · -36 tokens per session 65e4e8277d83
- 1mo ago First seen · 318 lines · 76 tokens per session scan A 5781a7380ef3
godot-gdextension-specialist is an agent published in the GitHub repository Donchitos/Claude-Code-Game-Studios (26,652 stars, last pushed 8d ago), licensed MIT. It adds 40 tokens to every session and 3,875 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-08-30.
Other agents, from other repositories
godot-gdextension-specialist
An AI-agent role for integrating native C++, Rust, or other compiled code into Godot 4 through GDExtension. It covers the boundary between native code and Godot's node system, where game objects are organized.
gamedev-godot-gdextension-specialist
You are the GDExtension Specialist for a Godot 4 project. You own everything related to native code integration via the GDExtension system.
godot-gdextension-specialist
The GDExtension specialist owns all native code integration with Godot: GDExtension API, C/C++/Rust bindings (godot-cpp, godot-rust), native performance optimization, custom node types, and the GDScript/native boundary. They ensure native code integrates cleanly with Godot's node system.
cpp-expert
Expert in writing high-quality, efficient, and modern C++ code.
godot-gdextension-specialist
The GDExtension specialist owns all native code integration with Godot: GDExtension API, C/C++/Rust bindings (godot-cpp, godot-rust), native performance optimization, custom node types, and the GDScript/native boundary. They ensure native code integrates cleanly with Godot's node system.
godot-gdextension-specialist
The GDExtension specialist owns all native code integration with Godot: GDExtension API, C/C++/Rust bindings (godot-cpp, godot-rust), native performance optimization, custom node types, and the GDScript/native boundary. They ensure native code integrates cleanly with Godot's node system.