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 CodePhobiia/claude-roblox-game-studio --skill launch-checklistgit clone --depth 1 https://github.com/CodePhobiia/claude-roblox-game-studioWrote 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/codephobiia/claude-roblox-game-studio/launch-checklist)<a href="https://agentmods.dev/skills/codephobiia/claude-roblox-game-studio/launch-checklist"><img src="https://agentmods.dev/badge/skills/codephobiia/claude-roblox-game-studio/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.
<a href="https://agentmods.dev/skills/codephobiia/claude-roblox-game-studio/launch-checklist"><img src="https://agentmods.dev/badge/skills/codephobiia/claude-roblox-game-studio/launch-checklist.svg" alt="Reviewed on agentmods" width="80" 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.00035 | $0.00939 |
| Opus 5 | $0.00017 | $0.00469 |
| Sonnet 5 | $0.00007 | $0.00188 |
| Haiku 4.5 | $0.00003 | $0.00094 |
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 9d 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/launch-checklist — First Launch Preparation
Delegate to: release-manager (with producer, analytics-retention-specialist, community-manager)
Unique to First Launch
First launches are higher-risk than updates — no existing player base to forgive bugs, and a bad first impression is hard to recover from. This checklist goes beyond /release-checklist with launch-specific considerations.
Phases
Phase 1: Soft Launch (Private Testing)
- Closed beta with ~50-200 testers
- Group invite-only or private server code
- Collect feedback via structured form
- Monitor crash rate, FPS, feedback quality
- Iterate on top 3 issues before public launch
Phase 2: Limited Public (Optional)
- Public but unadvertised — soft launch to see organic discovery
- Watch Discover page performance
- Verify critical metrics hold up at higher concurrency
- Fix any issues found in limited public before full marketing push
Phase 3: Marketing Push
- Content creator outreach kicks off
- Social media campaign active
- Paid ads running (if budget)
- Community events scheduled
- Launch trailer published
Phase 4: Launch Day
- All hands on deck for first 4-8 hours
- Real-time monitoring in place
- Quick-response plan for critical bugs
- Player support active (Discord mods)
- Press/community engagement
Critical Go/No-Go Criteria
Go Criteria (all must be true)
- No S0 bugs open
- No S1 bugs affecting core loop
- Crash rate < 1% in soft launch
- D1 retention in soft launch > 20% (prefer 25%+)
- Average session length > 10 minutes in soft launch
- Server costs manageable at projected launch CCU
- Team ready for launch-day support
- Rollback plan tested
No-Go Triggers
- Any S0 bug discovered in final testing
- Crash rate > 2% in soft launch
- DataStore failures > 0.5% of operations
- Server crashes > 5% of sessions
- Team burnout / not ready for launch support
- Competitive release same day (potential to delay)
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.
- 9d ago First seen · 117 lines · 35 tokens per session scan A 17035b12001e
launch-checklist is a skill published in the GitHub repository CodePhobiia/claude-roblox-game-studio (9 stars, last pushed 4mo ago), licensed MIT. It adds 35 tokens to every session and 939 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-08-31.
Other skills, from other repositories
gameobject-component-destroy
Destroy one or more Components from a target GameObject. Missing (null) components are skipped — they cannot be destroyed. Use 'gameobject-find' and 'gameobject-component-get' to identify the components first.
unity-version-split
Split a C# file into Unity 6.5+ and pre-Unity 6.5 variants. Use when a file needs different implementations for different Unity versions due to API changes (e.g., EntityId vs int, GetEntityId vs GetInstanceID).
unity-addressables
Manage Addressables groups, entries, profiles and content builds (com.unity.addressables, reflection-based).
motion
How an agent turns a character mesh into a usable animated FBX — and how to judge whether the result is shippable.
playtest-report
Generates a structured playtest report template or analyzes existing playtest notes into a structured format. Use this to standardize playtest feedback collection and analysis.
unity-manual-component
Manually add, configure, reorder, and copy components on GameObjects using Unity Editor UI. For one-off Inspector workflows that do not need REST automation.