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 gate-checkgit 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/gate-check)<a href="https://agentmods.dev/skills/codephobiia/claude-roblox-game-studio/gate-check"><img src="https://agentmods.dev/badge/skills/codephobiia/claude-roblox-game-studio/gate-check/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/gate-check"><img src="https://agentmods.dev/badge/skills/codephobiia/claude-roblox-game-studio/gate-check.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.00029 | $0.00954 |
| Opus 5 | $0.00015 | $0.00477 |
| Sonnet 5 | $0.00006 | $0.00191 |
| Haiku 4.5 | $0.00003 | $0.00095 |
Grade A, and why
gate-check 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/gate-check — Stage Gate Review
Delegate to: producer (with technical-director, qa-lead, creative-director for respective areas)
Purpose
Stage gates force a deliberate decision about whether to move to the next production phase. Without gates, projects drift — always "almost ready" to start production, or "almost ready" to ship.
Stages
Pre-production → Production
Gate criteria:
- Master GDD exists and reviewed
- Creative pillars defined (3-5, 1 phrase each)
- Core loop defined (30s / 5min / session / meta)
- Target audience identified
- Monetization strategy drafted
- Target metrics set (retention, session, revenue if applicable)
- Tech stack decided (sync tool, UI framework, packages)
- Systems-index exists with priority
- 2-3 top systems have detailed GDDs
- Prototype or proof-of-concept validates core loop
- Team capacity matches estimated scope (or scope cut accordingly)
Production → Polish
Gate criteria:
- All core systems implemented (from systems-index P0/P1)
- Game is playable end-to-end (intro → core loop → meta)
- No S0 bugs open
- All planned features either done or explicitly cut
- Basic performance targets met (30 FPS mobile, server heartbeat < 33ms)
- Security audit has been run at least once
- DataStore schema is frozen (no more breaking changes)
- Analytics events implemented
- At least one external playtest (not just devs) completed
Polish → Live (Launch Ready)
Gate criteria:
- Zero S0 bugs
- Zero S1 bugs in critical paths
- Performance targets exceeded on target devices
- Security audit passed with no Critical findings
- Content policy review passed
- All launch marketing materials ready
- Community channels active
- Rollback plan tested
- Soft launch retention > target (D1 > 20%, ideally > 25%)
- Server costs projected and manageable
- Team ready for launch support
Live → Live Service Optimization
Gate criteria (do we continue investing?):
- Retention trending up or stable
- Revenue meets minimum threshold
- Community engaged (growing Discord, positive reviews)
- Technical debt manageable
- Team has capacity for sustained live-ops
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 · 121 lines · 29 tokens per session scan A 6f6f58c35cc6
gate-check is a skill published in the GitHub repository CodePhobiia/claude-roblox-game-studio (9 stars, last pushed 4mo ago), licensed MIT. It adds 29 tokens to every session and 954 once invoked, about $0.0001 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…