launch-checklist

launch-checklist is a skill for Claude Code from Donchitos/Claude-Code-Game-Studios. It costs 30 tokens per session (4,004 once invoked), scanned A, original, MIT.

A checklist for deciding whether a game is ready to launch. It covers code, content, the store listing, marketing, community work, infrastructure, legal requirements, and approvals.

In plain words
What is it for?
Use it to inspect launch readiness across departments and collect the sign-offs needed for a go/no-go decision.
Why use it?
It reduces the chance that a non-code launch requirement is forgotten when the team focuses mainly on development.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: model in frontmatter; mentions CLAUDE.md; names the AskUserQuestion tool.

Good fit Use it to inspect launch readiness across departments and collect the sign-offs needed for a go/no-go decision.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/donchitos/claude-code-game-studios/launch-checklist
About the project

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.

Donchitos/Claude-Code-Game-Studios · 26,985 stars · on GitHub

Install

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.

Any agent
npx skills add Donchitos/Claude-Code-Game-Studios --skill launch-checklist
Clone the repo
git clone --depth 1 https://github.com/Donchitos/Claude-Code-Game-Studios

Made for: Claude Code.

Wrote 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.

agentmods badge for launch-checklist

README.md
[![agentmods](https://agentmods.dev/badge/skills/donchitos/claude-code-game-studios/launch-checklist/github.svg)](https://agentmods.dev/skills/donchitos/claude-code-game-studios/launch-checklist)
Your own site
<a href="https://agentmods.dev/skills/donchitos/claude-code-game-studios/launch-checklist"><img src="https://agentmods.dev/badge/skills/donchitos/claude-code-game-studios/launch-checklist/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.

agentmods 80×15 button for launch-checklist

Your own site · 80×15
<a href="https://agentmods.dev/skills/donchitos/claude-code-game-studios/launch-checklist"><img src="https://agentmods.dev/badge/skills/donchitos/claude-code-game-studios/launch-checklist.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 30 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,004 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
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.
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00030 $0.04004
Opus 5.5 $0.00012 $0.01602
Sonnet 5.5 $0.00006 $0.00801
Haiku 4.5 $0.00003 $0.00400

Measured yesterday against content hash ce8813df00b1, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

launch-checklist 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.

Origin

Copies of this mod

3 near-identical copies found in the catalogue:

.claude/skills/launch-checklist/SKILL.md · 390 lines

How it starts

The opening of the file, as written. The whole thing — 390 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 rigor,workflow,project.stage,cert_tier,automation

Automation mode: Resolve modes.automation (project.local.yaml → project.yaml → default collaborative). Every AskUserQuestion call and every file write follows .claude/docs/automation-modes.md (collaborative asks always · guided major-only · autonomous logs and proceeds; automation_always_ask categories always prompt).

Resolved above — use as-is. No block → defaults in .claude/docs/config-resolution.md.

Launch Checklist

Scope this checklist to the project. Emitting every item for every platform trains the reader to skip the list, which defeats the gate:

  • project.stage — items for phases this project has not reached are out of scope; say so rather than listing them unchecked.

  • modes.rigor — at minimal, drop items whose only justification is process weight this project has opted out of.

  • platform.cert_tier — emit certification items only for the tier the project targets. If it is unset, ask which platforms are in scope rather than emitting all of them — an unset value is a question, not a licence to emit every certification track. The answer, mapped onto the four values below, is the tier for this run. If it cannot be determined, mark the section NOT ASSESSED — cert tier unknown. Unset is not none: none is a decision, unset is a missing one, and they must not produce the same output. Branch on the four values this key takes — none | itch | steam | console — and not on platform names. The full requirement table is the ## platform.cert_tier section of .claude/docs/effects-map.md — read only that section (Grep its heading, then a bounded Read); the file as a whole is not a runtime input.

    • none — emit no certification section at all. Internal release, alpha or jam game. Say the section was omitted and why; do not leave it blank.
    • itch — itch.io upload requirements only: build size, page setup, age tags. No console and no Steamworks items.
    • steam — Steamworks: store page, depot build, achievements, system requirements, common content rules. No console certification items.
    • console — full platform certification (TRC / XR / Lotcheck), save-data rules, controller-mapping rules, age-rating boards. The heaviest tier.

    Branch on the cert_tier values above, not on platform names. A test on target platforms treats an itch project and a steam project identically, conflates none with unset, and keys on mobile, which is not a cert_tier value at all. Use the vocabulary the config defines.

If an item cannot be scoped because the config is absent, mark it NOT ASSESSED — platform/stage unknown. Do not silently include it: a rigor: standard, single-platform project would otherwise receive a ~150-item checklist demanding PC and console and mobile certification plus age ratings, of which ~140 are unassessable.


Read the full file on GitHub · 390 lines

Changes

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.

  1. yesterday Changed · -8 lines ce8813df00b1
  2. 12d ago Changed · +2 lines 80f02a816cfc
  3. 21d ago Changed · +49 lines 94da5745b2e9
  4. 26d ago Changed 96d5ce563828
  5. 27d ago Changed · +106 lines · -3 tokens per session 70cda413f7ff
  6. 1mo ago First seen · 241 lines · 33 tokens per session scan A 867e94f20e9b

Subscribe to this mod's changes

launch-checklist is a skill published in the GitHub repository Donchitos/Claude-Code-Game-Studios (26,985 stars, last pushed 2d ago), licensed MIT. It adds 30 tokens to every session and 4,004 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.

Related

Other skills, from other repositories

game-design

How game development works as a process — roles, subtasks, workflows and role descriptions, especially (but not only) for Roblox. Use this skill when it's about the ORGANIZATION of game dev rather than concrete code: Which roles exist (Creative Director, Engineer, Artist, Polish/Audio, Business, QA-Tester, Game…

ellmos-ai/skills · 176 tokens

rbx-dev

Meta-skill for complete Roblox game development with Rojo — the entry point that knows and unifies the three specialist skills /rojo (filesystem→Studio sync, project setup), /rbx-studio (editor, MCP, assets, malware scan) and /game-design (roles, workflows, GDD). Use this skill for ANY Roblox game-dev undertaking…

ellmos-ai/skills · 182 tokens

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.

ValorVie/custom-skills · 105 tokens

game-producer

Invoke when the user asks about sprint planning, milestone tracking, scope management, risk assessment, scheduling, resource allocation, team velocity, or needs production coordination across the development team. Triggers on: "sprint", "milestone", "scope", "risk", "schedule", "resource", "velocity", "deadline"…

AlterLab-IEU/AlterLab_GameForge · 111 tokens

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.

dewtech-technologies/dare-method · 76 tokens

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.

dewtech-technologies/dare-method · 0 tokens