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/hotfixnpx skills add Donchitos/Claude-Code-Game-Studios --skill hotfixgit 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/hotfix)<a href="https://agentmods.dev/skills/donchitos/claude-code-game-studios/hotfix"><img src="https://agentmods.dev/badge/skills/donchitos/claude-code-game-studios/hotfix.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.00035 | $0.01561 |
| Opus 5 | $0.00017 | $0.00781 |
| Sonnet 5 | $0.00007 | $0.00312 |
| Haiku 4.5 | $0.00003 | $0.00156 |
Grade A, and why
hotfix 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.
How it starts
The opening of the file, as written. The whole thing — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Explicit invocation only: This skill should only run when the user explicitly requests it with
/hotfix. Do not auto-invoke based on context matching.
Phase 1: Assess Severity
Read the bug description or ID. Assess severity using these criteria:
- S1 (Critical): Game unplayable, data loss, security vulnerability
- S2 (Major): Significant feature broken, workaround exists
- S3 or lower: Minor issue — normal bug fix workflow applies
Confirm with AskUserQuestion:
- Prompt: "I've assessed this as [assessed severity] — [brief rationale]. Confirm severity to proceed:"
- Options:
[A] S1 (Critical) — game unplayable, data loss, or security issue[B] S2 (Major) — significant feature broken, workaround exists[C] S3 or lower — redirect to normal bug fix workflow
If [C]: stop. Verdict: REDIRECTED — use the normal bug fix workflow for S3 and below.
Phase 2: Create Hotfix Record
Draft the hotfix record:
## Hotfix: [Short Description]
Date: [Date]
Severity: [S1/S2]
Reporter: [Who found it]
Status: IN PROGRESS
### Problem
[Clear description of what is broken and the player impact]
### Root Cause
[To be filled during investigation]
### Fix
[To be filled during implementation]
### Testing
[What was tested and how]
### Approvals
- [ ] Fix reviewed by lead-programmer
- [ ] Regression test passed (qa-tester)
- [ ] Release approved (producer)
### Rollback Plan
[How to revert if the fix causes new issues]
Ask: "May I write this to production/hotfixes/hotfix-[date]-[short-name].md?"
If yes, write the file, creating the directory if needed.
Phase 3: Create Hotfix Branch
Check whether this is a git repository:
Bash: git rev-parse --is-inside-work-tree 2>/dev/null
If this command fails or returns empty: note "Not a git repository — create the branch manually." and skip branch creation.
If the check passes, use AskUserQuestion before creating the branch:
- Prompt: "Ready to create hotfix branch 'hotfix/[short-name]' from [base-ref]?"
- Options:
[A] Yes — create branch[B] Use a different base ref — I'll specify it[C] Skip — I'll create the branch myself
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 · 181 lines · 35 tokens per session scan A 6d99a79bce37
hotfix is a skill published in the GitHub repository Donchitos/Claude-Code-Game-Studios (24,822 stars, last pushed 3mo ago), licensed MIT. It adds 35 tokens to every session and 1,561 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
security-audit
Java security checklist covering OWASP Top 10, input validation, injection prevention, and secure coding. Works with Spring, Quarkus, Jakarta EE, and plain Java. Use when reviewing code security, before releases, or when user asks about vulnerabilities.
solid-principles
SOLID principles checklist with Java examples. Use when a class has too many responsibilities, an abstraction leaks, or a dependency points the wrong way, and when the user asks about Single Responsibility, Open/Closed, Liskov, Interface Segregation or Dependency Inversion. For naming, duplication and method length…
issue-triage
Triage and categorize GitHub issues with priority labels. Use when user says "triage issues", "check issues", "review open issues", or during regular maintenance of GitHub issue backlog.
engineering-wisdom
Provide an explicitly requested, repository-grounded engineering review using contextual heuristics for code clarity, SOLID and design, testing, refactoring, architecture, and professional practice. Use only when the user invokes $engineering-wisdom or explicitly asks for this installed engineering-wisdom pack; do not…
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…
game-design
Use when designing or repairing what makes a game fun — verbs and mechanics, moment-to-moment/session/meta loops, progression, economy faucets and sinks, difficulty curves, dominant strategies, juice, prototyping and scope. NOT engine code (that is godot), NOT story (that is game-storytelling), NOT level layout (that…