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/sprint-statusnpx skills add Donchitos/Claude-Code-Game-Studios --skill sprint-statusgit 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/sprint-status)<a href="https://agentmods.dev/skills/donchitos/claude-code-game-studios/sprint-status"><img src="https://agentmods.dev/badge/skills/donchitos/claude-code-game-studios/sprint-status.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.00070 | $0.02013 |
| Opus 5 | $0.00035 | $0.01007 |
| Sonnet 5 | $0.00014 | $0.00403 |
| Haiku 4.5 | $0.00007 | $0.00201 |
Grade A, and why
sprint-status 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
4 near-identical copies found in the catalogue:
- sprint-status — 97% identical, 1 lines differ
- sprint-status — 95% identical, 10 lines differ
- sprint-status — 94% identical, 8 lines differ
- sprint-status — 91% identical, 32 lines differ
How it starts
The opening of the file, as written. The whole thing — 209 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sprint Status
This is a fast situational awareness check, not a sprint review. It reads the
current sprint plan and story files, scans for status markers, and produces a
concise snapshot in under 30 lines. For detailed sprint management, use
/sprint-plan update or /milestone-review.
This skill is read-only. It never proposes changes, never asks to write files, and makes at most one concrete recommendation.
1. Find the Sprint
Argument: $ARGUMENTS[0] (blank = use current sprint)
- If an argument is given (e.g.,
/sprint-status 3), searchproduction/sprints/for a file matchingsprint-03.md,sprint-3.md, or similar. Report which file was found. - If no argument is given, find the most recently modified file in
production/sprints/and treat it as the current sprint. - If
production/sprints/does not exist or is empty, report: "No sprint files found. Start a sprint with/sprint-plan new." Then stop.
Read the sprint file in full. Extract:
- Sprint number and goal
- Start date and end date
- All story or task entries with their priority (Must Have / Should Have / Nice to Have), owner, and estimate
2. Calculate Days Remaining
Using today's date and the sprint end date from the sprint file, calculate:
- Total sprint days (end minus start)
- Days elapsed
- Days remaining
- Percentage of time consumed
If the sprint file does not include explicit dates, note "Sprint dates not found — burndown assessment skipped."
3. Scan Story Status
First: check for production/sprint-status.yaml.
If it exists, read it directly — it is the authoritative source of truth.
Extract status for each story from the status field. No markdown scanning needed.
Use its sprint, goal, start, end fields instead of re-parsing the sprint plan.
If sprint-status.yaml does not exist (legacy sprint or first-time setup),
fall back to markdown scanning:
- If the entry references a story file path, check if the file exists. Read the file and scan for status markers: DONE, COMPLETE, IN PROGRESS, BLOCKED, NOT STARTED (case-insensitive).
- If the entry has no file path (inline task in the sprint plan), scan the sprint plan itself for status markers next to that entry.
- If no status marker is found, classify as NOT STARTED.
- If a file is referenced but does not exist, classify as MISSING and note it.
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 · 209 lines · 70 tokens per session scan A 58b80b7ee9a3
sprint-status is a skill published in the GitHub repository Donchitos/Claude-Code-Game-Studios (24,822 stars, last pushed 3mo ago), licensed MIT. It adds 70 tokens to every session and 2,013 once invoked, about $0.0003 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
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…
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.
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…