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/tech-debtnpx 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.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.00033 | $0.01267 |
| Opus 5 | $0.00016 | $0.00633 |
| Sonnet 5 | $0.00007 | $0.00253 |
| Haiku 4.5 | $0.00003 | $0.00127 |
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 3d 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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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 codebase 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
Present the findings to the user.
Ask: "May I write these findings to docs/tech-debt-register.md?"
If yes, update the register (append new entries, do not overwrite existing ones). Verdict: COMPLETE — scan findings written to register.
If no, stop here. Verdict: BLOCKED — user declined write.
Phase 2B: Add Mode
Ask the user for the description, affected files, and impact if left unfixed (plain text prompts).
Then use AskUserQuestion to collect the category:
- Prompt: "What category does this tech debt belong to?"
- Options:
[A] Architecture Debt — wrong abstractions, missing patterns, coupling issues[B] Code Quality Debt — duplication, complexity, naming, missing types[C] Test Debt — missing tests, flaky tests, untested edge cases[D] Documentation Debt — missing/outdated docs, undocumented APIs[E] Dependency Debt — outdated packages, deprecated APIs, version conflicts[F] Performance Debt — known slow paths, memory issues, unoptimized queries
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.
- 3d 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 (24,838 stars, last pushed 3mo ago), licensed MIT. It adds 33 tokens to every session and 1,267 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
ln-51-opportunity-evaluator
Evaluates new product opportunities using demand, channels, competition, and economics. Not for committed-backlog or implementation planning.
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.…
refactoring-assistant
Guide refactoring decisions and large-scale code improvements. Use when: refactoring code, legacy modernization, technical debt, rewrite decisions. Keywords: refactor, rewrite, legacy, strangler, technical debt, 重構, 重寫, 技術債.
spec-driven-dev
Guide Spec-Driven Development (SDD) workflow for planning changes before implementation. Use when: creating specs, proposals, planning features, using OpenSpec or similar tools. Keywords: spec, specification, SDD, proposal, openspec, design doc, 規格, 提案, 設計文件.
code-review-assistant
Systematic code review checklist and pre-commit quality gates for PRs. Use when: reviewing pull requests, checking code quality, before committing code. Keywords: review, PR, pull request, checklist, quality, commit, 審查, 檢查, 簽入.
requirement-assistant
Guide requirement writing, user story creation, and feature specification. Use when: writing requirements, user stories, issues, feature planning. Keywords: requirement, user story, issue, feature, specification, 需求, 功能規劃, 規格.