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 agentmods add skills/donchitos/claude-code-game-studios/security-auditnpx skills add Donchitos/Claude-Code-Game-Studios --skill security-auditgit 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/security-audit)<a href="https://agentmods.dev/skills/donchitos/claude-code-game-studios/security-audit"><img src="https://agentmods.dev/badge/skills/donchitos/claude-code-game-studios/security-audit.svg" alt="Measured on agentmods" 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.00049 | $0.01973 |
| Opus 5 | $0.00024 | $0.00986 |
| Sonnet 5 | $0.00010 | $0.00395 |
| Haiku 4.5 | $0.00005 | $0.00197 |
Grade A, and why
security-audit 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 2d 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
3 near-identical copies found in the catalogue:
- security-audit — 97% identical, 1 lines differ
- security-audit — 97% identical, 3 lines differ
- security-audit — 94% identical, 3 lines differ
How it starts
The opening of the file, as written. The whole thing — 246 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Audit
Security is not optional for any shipped game. Even single-player games have save tampering vectors. Multiplayer games have cheat surfaces, data exposure risks, and denial-of-service potential. This skill systematically audits the codebase for the most common game security failures and produces a prioritised remediation plan.
Run this skill:
- Before any public release (required for the Polish → Release gate)
- Before enabling any online/multiplayer feature
- After implementing any system that reads from disk or network
- When a security-related bug is reported
Output: production/security/security-audit-[date].md
Phase 1: Parse Arguments and Scope
Modes:
full— all categories (recommended before release)network— network/multiplayer onlysave— save file and serialization onlyinput— input validation and injection onlyquick— high-severity checks only (fastest, for iterative use)- No argument — run
full
Read .claude/docs/technical-preferences.md to determine:
- Engine and language (affects which patterns to search for)
- Target platforms (affects which attack surfaces apply)
- Whether multiplayer/networking is in scope
Phase 2: Spawn Security Engineer
Spawn security-engineer via Task. Pass:
- The audit scope/mode
- Engine and language from technical preferences
- A manifest of all source directories:
src/,assets/data/, any config files
The security-engineer runs the audit across 6 categories (see Phase 3). Collect their full findings before proceeding.
Phase 3: Audit Categories
The security-engineer evaluates each of the following. Skip categories not applicable to the project scope.
Category 1: Save File and Serialization Security
- Are save files validated before loading? (no blind deserialization)
- Are save file paths constructed from user input? (path traversal risk)
- Are save files checksummed or signed? (tamper detection)
- Does the game trust numeric values from save files without bounds checking?
- Are there any eval() or dynamic code execution calls near save loading?
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.
- 2d ago First seen · 246 lines · 49 tokens per session scan A b3d04c89f184
security-audit is a skill published in the GitHub repository Donchitos/Claude-Code-Game-Studios (24,822 stars, last pushed 3mo ago), licensed MIT. It adds 49 tokens to every session and 1,973 once invoked, about $0.0002 per session on Opus 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
novel-game-analyze
Deconstruct a novel for game adaptation. Compress a raw novel, deconstruction library, or writing project into a SOURCEBIBLE with cited textual evidence, extracting world rules, player verbs, spaces, character will, systems, and visual anchors — without inventing a genre yet. Use for gameable book analysis, analyze a…
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…
game-build
Build a risk-matched whitebox or the approved production game for its target runtime. Turn GAMEDESIGN, and ARTDIRECTION when production begins, into a minimal BUILDBRIEF and a runnable candidate that can be iterated with replayable evidence. Use for prototype the riskiest design question, implement the approved game…
game-concept
Design game concepts from a novel. From SOURCEBIBLE and PRODUCTBRIEF, generate three genuinely different directions on the dimensions still unlocked, then pick the most worthwhile playable prototype using hard vetoes and explicit trade-offs. Use for what game should this novel become, compare game concepts, choose a…
game-world-design
Design game experience, systems, and levels. Converge the chosen concept into one GAMEDESIGN defining the player promise, core loop, how the world responds, the systems actually needed, level pacing, feedback, failure, and a fully playable prototype. Use for design the game world, deepen the gameplay and levels, write…
game-qa
Verify a game with evidence on its selected target runtime. Launch the actual build and prove real rendering, input, the core loop, at least one designed outcome, restart, and explicit limitations without dressing subjective fun up as a certain verdict. Use for test a generated game, QA a game build, check whether the…