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/community-manager)<a href="https://agentmods.dev/agents/donchitos/claude-code-game-studios/community-manager"><img src="https://agentmods.dev/badge/agents/donchitos/claude-code-game-studios/community-manager/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/community-manager"><img src="https://agentmods.dev/badge/agents/donchitos/claude-code-game-studios/community-manager.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.01840 |
| Opus 5.5 | $0.00011 | $0.00736 |
| Sonnet 5.5 | $0.00005 | $0.00368 |
| Haiku 4.5 | $0.00003 | $0.00184 |
Grade A, and why
community-manager 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
6 near-identical copies found in the catalogue:
- community-manager — 100% identical, 69 lines differ
- community-manager — 100% identical, 69 lines differ
- community-manager — 100% identical, 69 lines differ
- community-manager — 100% identical, 69 lines differ
- community-manager — 94% identical, 76 lines differ
- community-manager — 81% identical, 81 lines differ
How it starts
The opening of the file, as written. The whole thing — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Community Manager for a game project. You own all player-facing communication and community engagement.
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:
- "Who is the audience, and what tone fits (patch notes, dev blog, incident update)?"
- "What has QA actually confirmed as fixed, so nothing is claimed without evidence?"
- "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 prepare the short social variants?"
- "Want the known-issues section checked with qa-lead before this goes out?"
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 · -3 lines 5d75220aace9
- 25d ago Changed · +8 lines · -18 tokens per session c40cf6183bb8
- 1mo ago First seen · 158 lines · 45 tokens per session scan A ba552c736a42
community-manager is an agent published in the GitHub repository Donchitos/Claude-Code-Game-Studios (26,822 stars, last pushed 11d ago), licensed MIT. It adds 27 tokens to every session and 1,840 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
context-engineer
Expert in creating and refining all types of Claude Code resources: sub-agents, skills, plugins, slash commands, hooks, specs, workflows, templates, and patterns. Specializes in context engineering with deep knowledge of Claude SDK architecture, Anthropic best practices, and production-ready implementation patterns.…
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.
aws-cloud-architect
AWS cloud infrastructure architect specializing in designing, implementing, and optimizing scalable AWS solutions. Use for AWS service selection, architecture design, cost optimization, and security best practices for EC2, EKS, Fargate, and other AWS services.
python-data-engineer
Expert in Python data engineering, ETL pipelines, and production data systems. Specializes in modern data pipeline architecture, Pandas/Polars/PySpark, Apache Airflow orchestration, and data warehouse design.
go-expert
Go specialist focusing on idiomatic Go, concurrency, and performance optimization.
security-auditor
Use this agent when you need to perform a comprehensive security audit of a codebase, identify vulnerabilities, and generate a detailed security report with actionable remediation steps. This includes reviewing authentication mechanisms, input validation, data protection, API security, dependencies, and infrastructure…