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 patch-notesgit 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/patch-notes)<a href="https://agentmods.dev/skills/donchitos/claude-code-game-studios/patch-notes"><img src="https://agentmods.dev/badge/skills/donchitos/claude-code-game-studios/patch-notes/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/patch-notes"><img src="https://agentmods.dev/badge/skills/donchitos/claude-code-game-studios/patch-notes.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 7 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
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.00024 | $0.02304 |
| Opus 5.5 | $0.00010 | $0.00922 |
| Sonnet 5.5 | $0.00005 | $0.00461 |
| Haiku 4.5 | $0.00002 | $0.00230 |
Grade A, and why
patch-notes 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 today.
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
4 near-identical copies found in the catalogue:
- patch-notes — 100% identical, 85 lines differ
- patch-notes — 94% identical, 89 lines differ
- patch-notes — 94% identical, 88 lines differ
- patch-notes — 83% identical, 102 lines differ
How it starts
The opening of the file, as written. The whole thing — 252 lines — stays where its author put it; the contents beside it link to each section on GitHub.
!bash "${CLAUDE_SKILL_DIR}/../../hooks/yaml-helper.sh" resolve_config --keys automation
Automation mode: Resolve modes.automation (project.local.yaml →
project.yaml → default collaborative). Every AskUserQuestion call and
every file write follows .claude/docs/automation-modes.md
(collaborative asks always · guided major-only · autonomous logs and proceeds;
automation_always_ask categories always prompt).
Patch Notes
Provenance check — before reading any history
Confirm the history you are about to read belongs to THIS game. Run this before Phase 2 and stop if it fails.
- Sample the recent log:
git log --oneline -20. If it is empty or git is unavailable, skip this check — there is nothing to classify, and Phase 2's no-changelog-data branch is the right stop. - Classify every commit in the range, one at a time, into exactly one of:
- Game — changes the game the player plays: mechanics, content, balance, art, audio, UI, a bug in any of those.
- Framework / maintenance — changes CCGS itself or the project's tooling: subjects naming skills, hooks, agents, the test plan, CI, the framework's own docs. Excluded from player-facing notes, but not a reason to stop.
- Unclear — treat as framework. A commit you cannot confidently place is not one to write player copy from.
- Then decide from the counts:
- At least one Game commit → proceed, using only those. Say how many of how many you used, so the reader can see the filter ran.
- Zero Game commits → stop, using the message below, and give the count (0 of how many) so the reader can see the filter ran.
Filter per commit; do not stop on a repo that merely contains maintenance work. Every project built on this framework accumulates commits touching hooks, CI and skills — the game repo is the framework repo, so a repo-level stop fires on virtually every real project. The danger is not that such commits exist; it is that they get rendered as player-facing copy. Excluding them addresses that exactly, and a repo-level stop does not.
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.
- today Changed · -4 lines 41e7a4b4b1d5
- 11d ago Changed · +2 lines b46da0c3339b
- 20d ago Changed · +12 lines 23cf1e7ae25b
- 25d ago Changed c713d62f5396
- 26d ago Changed · +55 lines · -9 tokens per session af905f79e2b7
- 1mo ago First seen · 187 lines · 33 tokens per session scan A ffb34d12e0d3
patch-notes is a skill published in the GitHub repository Donchitos/Claude-Code-Game-Studios (26,893 stars, last pushed yesterday), licensed MIT. It adds 24 tokens to every session and 2,304 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-09-03.
Other skills, from other repositories
game-design
How game development works as a process — roles, subtasks, workflows and role descriptions, especially (but not only) for Roblox. Use this skill when it's about the ORGANIZATION of game dev rather than concrete code: Which roles exist (Creative Director, Engineer, Artist, Polish/Audio, Business, QA-Tester, Game…
rbx-dev
Meta-skill for complete Roblox game development with Rojo — the entry point that knows and unifies the three specialist skills /rojo (filesystem→Studio sync, project setup), /rbx-studio (editor, MCP, assets, malware scan) and /game-design (roles, workflows, GDD). Use this skill for ANY Roblox game-dev undertaking…
novel-to-game
Turn a novel into a fully playable game on the selected target platform. Orchestrates the whole adaptation pipeline — requirements intake, gameable deconstruction, concept selection, world and visual design, target-runtime build, and evidence-based QA — for a novel in any language. Use for novel to game, story to…
media-higgsfield-assets
A Higgsfield workflow for creating or processing media beyond ordinary image and video generation. It covers 3D GLB models, rigging and animation, audio, video analysis, upscaling, reframing, outpainting, and background removal.
gamemaker-gml
Best practices for GameMaker Language (GML) development, covering scripts, object events, rooms, data structures, and performance-minded game code. Use when writing GML scripts or object event code in GameMaker Studio, structuring create/step/draw events, managing rooms and instances, building state machines for…
wow-assistant
Context-aware World of Warcraft lore, progressive hints, builds, and PvP/PvE guidance using the Nanocodex WoW companion's exported character snapshot.