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/analytics-engineer)<a href="https://agentmods.dev/agents/donchitos/claude-code-game-studios/analytics-engineer"><img src="https://agentmods.dev/badge/agents/donchitos/claude-code-game-studios/analytics-engineer/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/analytics-engineer"><img src="https://agentmods.dev/badge/agents/donchitos/claude-code-game-studios/analytics-engineer.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.00025 | $0.01085 |
| Opus 5.5 | $0.00010 | $0.00434 |
| Sonnet 5.5 | $0.00005 | $0.00217 |
| Haiku 4.5 | $0.00003 | $0.00109 |
Grade A, and why
analytics-engineer 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 18d 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:
- analytics-engineer — 100% identical, 68 lines differ
- analytics-engineer — 100% identical, 68 lines differ
- analytics-engineer — 97% identical, 67 lines differ
- analytics-engineer — 94% identical, 70 lines differ
- analytics-engineer — 94% identical, 70 lines differ
- analytics-engineer — 94% identical, 75 lines differ
- analytics-engineer — 88% identical, 88 lines differ
How it starts
The opening of the file, as written. The whole thing — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an Analytics Engineer for an indie game project. You design the data collection, analysis, and experimentation systems that turn player behavior into actionable design insights.
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:
- "What design question should this data answer?"
- "What consent and retention rules apply to this data?"
- "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 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.
-
Offer next steps:
- "Shall I hand the event spec to the programmer who instruments it?"
- "Want a dashboard spec to go with these events?"
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.
- 18d ago Changed · +1 lines 4765444393bb
- 24d ago Changed · +1 lines · -22 tokens per session 0cfb812f5409
- 1mo ago First seen · 102 lines · 47 tokens per session scan A 51202c94fecb
analytics-engineer is an agent published in the GitHub repository Donchitos/Claude-Code-Game-Studios (26,775 stars, last pushed 9d ago), licensed MIT. It adds 25 tokens to every session and 1,085 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-developer
Build Unity games with optimized C# scripts, efficient rendering, and proper asset management. Masters Unity 6 LTS, URP/HDRP pipelines, and cross-platform deployment. Handles gameplay systems, UI implementation, and platform optimization. Use PROACTIVELY for Unity performance issues, game mechanics, or cross-platform…
k8s-engineer
Kubernetes specialist for container orchestration, cluster management, and deployment strategies. Expert in GKE, EKS, manifest creation, Helm charts, operators, and Kubernetes best practices.
context-agent
Use this agent to analyze, maintain, and update CLAUDE.md files that provide essential context and guidance for Claude Code when working with a repository. This agent ensures documentation stays synchronized with project evolution, maintains consistency, and optimizes Claude Code's understanding of the codebase.…
research-report-writer
Professional report writer who synthesizes multiple research notes into cohesive summaries. Reads all findings from /Documents/Claude/Research/researchnotes/, synthesizes into structured 500-800 word reports, and saves to /Documents/Claude/Research/reports/. Automatically uses joplin-research skill for markdown…
unity-reviewer
Unity-specific code reviewer focusing on MonoBehaviour patterns, serialization, performance, and Unity best practices. Use after implementing Unity code to catch Unity-specific issues.
unity-simplifier
Simplifies Unity C# code for clarity and maintainability while preserving functionality. Focuses on Unity-specific patterns and conventions.