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 estimategit 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/estimate)<a href="https://agentmods.dev/skills/donchitos/claude-code-game-studios/estimate"><img src="https://agentmods.dev/badge/skills/donchitos/claude-code-game-studios/estimate/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/estimate"><img src="https://agentmods.dev/badge/skills/donchitos/claude-code-game-studios/estimate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- 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.00020 | $0.01379 |
| Opus 5.5 | $0.00008 | $0.00552 |
| Sonnet 5.5 | $0.00004 | $0.00276 |
| Haiku 4.5 | $0.00002 | $0.00138 |
Grade A, and why
estimate 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.
How it starts
The opening of the file, as written. The whole thing — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Estimate
Phase 1: Understand the Task
Read the task description from the argument. If the description is too vague to estimate meaningfully, ask for clarification before proceeding.
Read CLAUDE.md for project context: tech stack, coding standards, architectural patterns, and any estimation guidelines.
Read relevant design documents from design/gdd/ if the task relates to a documented feature or system. Read them by section: find the headings you need with the Grep tool (pattern ^#, content mode) and Read those ranges with offset and limit.
Phase 2: Scan Affected Code
Identify files and modules that would need to change:
- Measure size and branching with Grep, per affected file — Read, Glob and Grep
are this skill's only tools, so these counts are the measurement:
- Size:
Grep pattern="[^[:space:]]" path="[file]" output_mode="count"— non-blank lines. - Branching:
Grep pattern="(^|[^A-Za-z0-9_])(if|elif|for|foreach|while|match|switch|case|catch)([^A-Za-z0-9_]|$)|&&|[|][|]" path="[file]" output_mode="count"— lines holding a branch or a boolean operator. The count approximates cyclomatic complexity (comments and strings count too); report it as that, never as a measured complexity. - Dependencies: what each file pulls in —
preload/load((GDScript),using(C#),#include(C++) — and which other files reference it. - Name any file Grep could not count (missing, binary, unreadable) under Notes and Assumptions rather than leaving it out of the totals.
- Size:
- Identify integration points with other systems
- Check for existing test coverage in the affected areas
- Read past sprint data from
production/sprints/for similar completed tasks and historical velocity. If there is none, say so under Notes and Assumptions — "No sprint history found; this estimate is not calibrated to the team's velocity" — and treat that as a risk in the confidence level, not as a silent padding of the figures.
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 · +12 lines 61d821627b3d
- 11d ago Changed · +2 lines 0b054f7a62b9
- 20d ago Changed · +4 lines cee5d4daeaed
- 26d ago Changed · -8 tokens per session f2a3388d11e5
- 1mo ago First seen · 133 lines · 28 tokens per session scan A 7774e2d256a0
estimate is a skill published in the GitHub repository Donchitos/Claude-Code-Game-Studios (26,893 stars, last pushed yesterday), licensed MIT. It adds 20 tokens to every session and 1,379 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
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.