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 tech-debtgit 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/tech-debt)<a href="https://agentmods.dev/skills/donchitos/claude-code-game-studios/tech-debt"><img src="https://agentmods.dev/badge/skills/donchitos/claude-code-game-studios/tech-debt/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/tech-debt"><img src="https://agentmods.dev/badge/skills/donchitos/claude-code-game-studios/tech-debt.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.00025 | $0.02528 |
| Opus 5.5 | $0.00010 | $0.01011 |
| Sonnet 5.5 | $0.00005 | $0.00506 |
| Haiku 4.5 | $0.00003 | $0.00253 |
Grade A, and why
tech-debt 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 yesterday.
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 — 219 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,workflow
Tech Debt
Every AskUserQuestion call follows .claude/docs/automation-modes.md
(collaborative asks always · guided major-only · autonomous logs and proceeds;
automation_always_ask categories always prompt).
Phase 1: Parse Subcommand
Determine the mode from the argument:
scan— Scan the codebase for tech debt indicatorsadd— Add a new tech debt entry manuallyprioritize— Re-prioritize the existing debt registerreport— Generate a summary report of current debt status
If no subcommand is provided, output usage and stop. Verdict: FAIL — missing required subcommand.
Phase 2A: Scan Mode
Search the code root (resolve per .claude/docs/code-root-resolution.md:
src/, Assets/ or Source/ by engine) for debt indicators:
TODOcomments (count and categorize)FIXMEcomments (these are bugs disguised as debt)HACKcomments (workarounds that need proper solutions)@deprecatedmarkers- Duplicated code blocks (similar patterns in multiple files)
- Files over 500 lines (potential god objects)
- Functions over 50 lines (potential complexity)
Categorize each finding:
- Architecture Debt: Wrong abstractions, missing patterns, coupling issues
- Code Quality Debt: Duplication, complexity, naming, missing types
- Test Debt: Missing tests, flaky tests, untested edge cases
- Documentation Debt: Missing docs, outdated docs, undocumented APIs
- Dependency Debt: Outdated packages, deprecated APIs, version conflicts
- Performance Debt: Known slow paths, unoptimized queries, memory issues
Before presenting anything, establish that there was something to scan.
Count the source files the scan actually covered. If the code root is
unresolved, report NOT ASSESSED — code root unresolved and stop as below. If
that count is zero — the code root is absent, or holds no source files — report:
NOT ASSESSED — no source files to scan. The code root contains no code, so "no debt indicators found" would be a statement about an empty search, not about the codebase. Run this once implementation is under way.
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.
- yesterday Changed · +6 lines 11299c8a1702
- 12d ago Changed · +2 lines bec31edccac3
- 21d ago Changed · +46 lines db5118f6924d
- 26d ago Changed 9fbeddba114a
- 27d ago Changed · +24 lines · -8 tokens per session 2430c6203151
- 1mo ago First seen · 141 lines · 33 tokens per session scan A bebf9faf308e
tech-debt is a skill published in the GitHub repository Donchitos/Claude-Code-Game-Studios (26,985 stars, last pushed 2d ago), licensed MIT. It adds 25 tokens to every session and 2,528 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
feature-dev
Guide a feature implementation through a structured seven-phase workflow with deep codebase understanding, clarifying questions, parallel architecture design, and quality review. Use this skill when the user asks to build a new feature, add functionality, or wants a methodical approach to implementation rather than…
github-triage
Read-only GitHub triage for issues AND PRs. 1 item = 1 background task (category: quick). Analyzes all open items and writes evidence-backed reports to /tmp/{datetime}/. Every claim requires a GitHub permalink as proof. NEVER takes any action on GitHub - no comments, no merges, no closes, no labels. Reports only.…
assess-pr
The /assess end-of-run offers - open a PR with the report, track the Top 3 Actions in the user's issue tracker, freeze the assessment into a CI gate, and file tool feedback. TRIGGER when the /assess orchestrator reaches the end-of-run offers; not a standalone user command.
project-onboarding
Standard procedure for onboarding new software projects: Feature analysis, code quality review, onboarding checklist, and task creation.
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.
address-conductor-comment
A workflow for handling pending Conductor code-review comments, including reading their discussion and assigning changes to subagents when appropriate.