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 studio-testgit 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/studio-test)<a href="https://agentmods.dev/skills/codephobiia/claude-roblox-game-studio/studio-test"><img src="https://agentmods.dev/badge/skills/codephobiia/claude-roblox-game-studio/studio-test/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/studio-test"><img src="https://agentmods.dev/badge/skills/codephobiia/claude-roblox-game-studio/studio-test.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.00044 | $0.00554 |
| Opus 5 | $0.00022 | $0.00277 |
| Sonnet 5 | $0.00009 | $0.00111 |
| Haiku 4.5 | $0.00004 | $0.00055 |
Grade A, and why
studio-test 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.
What it actually says
/studio-test — Automated Play Test
Delegate to: studio-mcp-operator
Steps
1. Connect to Studio
mcp__roblox-studio__list_roblox_studios— verify Studio is openmcp__roblox-studio__set_active_studio— select the correct instance
2. Pre-Test Check
mcp__roblox-studio__search_game_tree— verify key services exist (ServerScriptService, ReplicatedStorage)mcp__roblox-studio__get_console_output— clear/note any pre-existing errors
3. Start Play Test
mcp__roblox-studio__start_stop_play— start play mode- Wait 3-5 seconds for game initialization
4. Verify Runtime State
mcp__roblox-studio__execute_luau— run verification checks:- Are core services initialized?
- Do expected RemoteEvents exist in ReplicatedStorage?
- Is player data loading without errors?
- Are any scripts erroring?
5. Capture Visual State
mcp__roblox-studio__screen_capture— screenshot the game- Analyze: Is the UI rendering? Is the world visible? Any obvious visual issues?
6. Check Console
mcp__roblox-studio__get_console_output— read all output since play started- Flag: errors (red), warnings (yellow), unexpected prints
- Categorize: script errors, DataStore errors, remote errors, asset loading errors
7. Stop Play Test
mcp__roblox-studio__start_stop_play— stop play mode
8. Report Results
# Play Test Report
**Status**: [PASS / FAIL / WARNINGS]
**Duration**: X seconds
**Studio**: [instance name]
## Console Output
- Errors: [count]
- Warnings: [count]
- [List each error with source script and message]
## Runtime Verification
- [x] Core services loaded
- [x] Remotes exist
- [ ] Player data initialized (FAILED: DataStore timeout)
## Visual Check
- [Screenshot attached]
- [Any visual issues noted]
## Recommendations
1. [Fix needed]
2. [Investigation needed]
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 · 69 lines · 44 tokens per session scan A c0594730a71f
studio-test is a skill published in the GitHub repository CodePhobiia/claude-roblox-game-studio (9 stars, last pushed 4mo ago), licensed MIT. It adds 44 tokens to every session and 554 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
develop-web-game
Use when Codex is building or iterating on a web game (HTML/JS) and needs a reliable development + testing loop: implement small changes, run a Playwright-based test script with short input bursts and intentional pauses, inspect screenshots/text, and review console errors with rendergametotext.
tests-run
Execute Unity tests (EditMode or PlayMode) and return per-test results. Supports filtering by test assembly, namespace, class, and method. Refreshes the AssetDatabase first; defers execution across domain reloads if scripts changed. Precondition: every open scene must be saved — dirty scenes abort the run.
unity-agent-workflows
Use for AI-assisted Unity work that needs live repo discovery, project-derived routing, runtime-owner proof, runtime-visible output hard stops, runtime numeric proof for repeated visible-output failures, state-step guards, multi-agent scope ownership, modular C#/asmdef safety, UI/scene/visual asset gates, data-first…
sprite-gen
A pipeline for turning generated 2D game-character images into transparent sprite sheets, which store animation frames for a game.
testing-bgs-modpack
A checklist and decision guide for checking a newly installed batch of Bethesda Game Studios game modifications before accepting it as ready.
gdunit-driver
Run gdUnit4 unit tests and parse results into structured output. Use this skill after writing or modifying code to verify correctness via unit tests, when diagnosing test failures, or when writing new test files. Triggers: "run tests", "test fails", "write a test", any gdUnit4/unit test mention. Supports both GDScript…