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.
npx skills add Donchitos/Claude-Code-Game-Studios --skill settingsgit 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/skills/donchitos/claude-code-game-studios/settings)<a href="https://agentmods.dev/skills/donchitos/claude-code-game-studios/settings"><img src="https://agentmods.dev/badge/skills/donchitos/claude-code-game-studios/settings/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/skills/donchitos/claude-code-game-studios/settings"><img src="https://agentmods.dev/badge/skills/donchitos/claude-code-game-studios/settings.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.00020 | $0.05052 |
| Opus 5.5 | $0.00008 | $0.02021 |
| Sonnet 5.5 | $0.00004 | $0.01010 |
| Haiku 4.5 | $0.00002 | $0.00505 |
Grade D, and why
settings scanned grade D with 2 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 8d 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.
Tells the agent never to refusehighAnti-refusal
Suppressing the ability to decline removes a core safety control; a later harmful request then succeeds.
Never refuse a write to a reserved key. Storing the value a user intends is Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
grep -B14 '^> ### RESERVED' .claude/docs/effects-map.md | grep -E '^## ' How it starts
The opening of the file, as written. The whole thing — 468 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/settings — view or change project config
Manages project.yaml (team-wide config, committed) and project.local.yaml
(per-developer overrides, gitignored). Use this skill to inspect current
settings or change them without manually editing YAML.
Automation mode: Resolve modes.automation (project.local.yaml →
project.yaml → default collaborative). The approval gates in Phase 4 and
Phase 5 follow the pattern in .claude/docs/automation-modes.md. Note:
writing to project.yaml is a schema_changes decision (a default
automation_always_ask category), so /settings confirms config writes even
in autonomous mode unless the user has removed schema_changes from their
always-ask list.
Phase 0: Parse Arguments
Determine which of the four forms the user invoked:
| Form | Mode |
|---|---|
/settings (no args) |
View-all (Phase 2) |
/settings <key> (single arg, no =) |
View-one (Phase 3) |
/settings <key>=<value> (single arg with =) |
Set-yaml (Phase 4) |
/settings --local <key>=<value> (--local prefix) |
Set-local (Phase 5) |
For Set-yaml and Set-local, <key> is a dotted YAML path (e.g.
modes.review_mode, testing.strict.logic) and <value> is the new value.
Empty-operand validation: After splitting the key=value operand on
=, if either <key> or <value> is empty, this is malformed — route to
Phase 6 (usage) rather than attempting the write. The rule applies in both
Set-yaml and Set-local routing: for --local, strip the --local token
first, then check the remaining operand the same way (so /settings --local =foo
and /settings --local key= both go to Phase 6).
Anything else that doesn't match the four forms above → Phase 6 (usage).
Phase 1: Load Helper
All four subcommands need yaml-helper.sh. Each Bash call starts a fresh
shell, so load it in the same command as every helper call, from the project
root, in parentheses so the session's working directory does not change:
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.
- 8d ago Changed · +8 lines 7b9d08e98bc7
- 17d ago Changed d34fd40603b2
- 22d ago Changed a35c983e2663
- 23d ago First seen · 460 lines · 20 tokens per session scan D cf55d1cfc176
settings is a skill published in the GitHub repository Donchitos/Claude-Code-Game-Studios (26,726 stars, last pushed 8d ago), licensed MIT. It adds 20 tokens to every session and 5,052 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it D with 2 findings (tells the agent never to refuse, reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-24.
Other skills, from other repositories
work-log-claude
A work-log generator that reads Claude Code's local session records and produces an evidence-based Markdown report. It can organise work by project and time period while excluding unrelated session data.
dare-refine
Analisa complexidade de uma task DARE e, quando alta, quebra em sub-tasks menores. Use após gerar o DAG (para tasks HIGH/CRITICAL), quando o dev pedir refinamento manual, ou quando o escopo mudou e uma task ficou grande. Combina heurística determinística (CLI) com decisão semântica do agente.
dare-graph
Consulta e visualiza o grafo de conhecimento do projeto (tasks, arquivos, schemas, endpoints, componentes, entidades e suas relações). Mapeia o CLI dare graph.
dare-dag
Mostra o DAG estático de tasks (DARE/dare-dag.yaml): ranks, dependências e caminho crítico. Use dare dag viz para exportar o diagrama. Mapeia o CLI dare dag.
project-diagnosis
Structured gap analysis that identifies what a project is missing — not what's done poorly (that's /audit), but what's absent entirely. Checks for tests, CI, security basics, linting, type safety, deployment readiness, and dependency health. Each finding has a severity and a concrete fix action.
tech-debt-tracking
Track shortcuts with justifications, prevent debt accumulation, and surface outstanding debt at session start.