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 AshExplained/roblox-skills --skill roblox-playtest-qagit clone --depth 1 https://github.com/AshExplained/roblox-skillsWrote 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/ashexplained/roblox-skills/roblox-playtest-qa)<a href="https://agentmods.dev/skills/ashexplained/roblox-skills/roblox-playtest-qa"><img src="https://agentmods.dev/badge/skills/ashexplained/roblox-skills/roblox-playtest-qa/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/ashexplained/roblox-skills/roblox-playtest-qa"><img src="https://agentmods.dev/badge/skills/ashexplained/roblox-skills/roblox-playtest-qa.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.00039 | $0.00438 |
| Opus 5 | $0.00019 | $0.00219 |
| Sonnet 5 | $0.00008 | $0.00088 |
| Haiku 4.5 | $0.00004 | $0.00044 |
Grade A, and why
roblox-playtest-qa 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 10d 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
Roblox Playtest QA
Purpose
Use this skill to verify that a Roblox change works in Studio and supports player-facing quality. A playtest should prove both behavior and feel.
Setup
- Run
list_roblox_studios. - Use
set_active_studioif needed. - Run
get_studio_state. - Start play mode with
start_stop_playwhen verification requires live behavior.
Test Checklist
- First action is reachable within 10-30 seconds.
- Controls work without keyboard-only assumptions.
- HUD text is readable and not blocking gameplay.
- Rewards, currency, XP, or progress update correctly.
- The next objective is visible after each loop.
- Social features are visible early when relevant.
- Monetization prompts are optional and do not interrupt first-session flow.
- Server-side systems own valuable state.
- No obvious frame drops or runaway instance/script growth.
get_console_outputhas no new errors.
MCP Tools To Use
character_navigationfor movement and route checks.user_keyboard_inputanduser_mouse_inputfor controls and UI.screen_capturefor visual verification.get_console_outputfor errors and warnings.inspect_instanceorexecute_luaufor state checks after interaction.
Report Format
Return:
- What was tested.
- Evidence gathered, including screenshots or console results when available.
- Pass/fail by area.
- Bugs or risks ranked by player impact.
- Recommended next verification step.
Do not mark roadmap items complete without human approval, even after a passing playtest.
Next
Send any bug to roblox-debugging-bugfix and any performance issue to roblox-performance-optimization. If the slice passes, mark it in roblox-triage / ROADMAP.md and prepare the build with roblox-release-operations.
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.
- 10d ago First seen · 56 lines · 39 tokens per session scan A 615673b1595c
roblox-playtest-qa is a skill published in the GitHub repository AshExplained/roblox-skills (6 stars, last pushed 2mo ago), licensed MIT. It adds 39 tokens to every session and 438 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
agent-browser
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
smoke-check
Run the critical path smoke test gate before QA hand-off. Executes the automated test suite, verifies core functionality, and produces a PASS/FAIL report. Run after a sprint's stories are implemented and before manual QA begins. A failed smoke check means the build is not ready for QA.
hearth-playtest
Let the engine hunt bugs for you — bot playtesting via hearth sweep. Seeded bot policies (mash/idle/wander/seek) play a scene headlessly across many seeds and report softlocks, crashes, stuck states, and unmet objectives as a compact evidence report; objectives double as executable acceptance criteria; a failing seed…
writing-tests
Write unit, integration, and E2E tests that follow the testing pyramid, the Arrange-Act-Assert pattern, the shouldXwhenY naming convention, and meet a 75% (target 80%) branch coverage gate per supported OS. Use when the user asks to write tests, add coverage, build a test suite, fix flaky tests, or verify a feature…
webapp-testing
Verify a web application works correctly in a real browser using Playwright. Covers page navigation, form submission, user interactions, console error detection, screenshot capture, and responsive layout checking. Use when you need to confirm a UI feature actually works end-to-end, catch regressions after a change…
gm-evaluate
Evaluate the current tag's quality: enforce the playable-closed-loop gate, maintain a single cross-tag e2e/ suite that always reflects the current game (add tests for new mechanics, prune tests for mechanics this tag deliberately removed), and reason about gameplay quality. Independent from the build process — fresh…