roblox-playtest-qa

roblox-playtest-qa is a skill for Claude Code, Codex from AshExplained/roblox-skills. It costs 39 tokens per session (438 once invoked), scanned A, original, MIT.

A testing guide for Roblox games that checks both whether changes work and what a new player experiences in Roblox Studio.

In plain words
What is it for?
Use it to playtest movement, interfaces, rewards, social features, performance, and security-sensitive game flows across supported inputs.
Why use it?
It helps catch broken controls, unclear progression, console errors, performance problems, and poor first-session usability.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to playtest movement, interfaces, rewards, social features, performance, and security-sensitive game flows across supported inputs.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/ashexplained/roblox-skills/roblox-playtest-qa
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 AshExplained/roblox-skills --skill roblox-playtest-qa
Clone the repo
git clone --depth 1 https://github.com/AshExplained/roblox-skills

Made for: Claude Code, Codex.

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 roblox-playtest-qa

README.md
[![agentmods](https://agentmods.dev/badge/skills/ashexplained/roblox-skills/roblox-playtest-qa/github.svg)](https://agentmods.dev/skills/ashexplained/roblox-skills/roblox-playtest-qa)
Your own site
<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.

agentmods 80×15 button for roblox-playtest-qa

Your own site · 80×15
<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>
Per session 39 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 438 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.
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.00039 $0.00438
Opus 5 $0.00019 $0.00219
Sonnet 5 $0.00008 $0.00088
Haiku 4.5 $0.00004 $0.00044

Measured 10d ago against content hash 615673b1595c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

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.

roblox-playtest-qa/SKILL.md · 56 lines

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

  1. Run list_roblox_studios.
  2. Use set_active_studio if needed.
  3. Run get_studio_state.
  4. Start play mode with start_stop_play when 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_output has no new errors.

MCP Tools To Use

  • character_navigation for movement and route checks.
  • user_keyboard_input and user_mouse_input for controls and UI.
  • screen_capture for visual verification.
  • get_console_output for errors and warnings.
  • inspect_instance or execute_luau for 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.

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. 10d ago First seen · 56 lines · 39 tokens per session scan A 615673b1595c

Subscribe to this mod's changes

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.

Related

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.

code-yeongyu/oh-my-openagent · 51 tokens

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.

striderZA/OpenCodeGameStudios · 61 tokens

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…

echoo19/hearth · 112 tokens

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…

Cristhianzl/claude-skills-czl · 103 tokens

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…

KhaledSaeed18/dotclaude · 91 tokens

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…

RandallLiuXin/GodotMaker · 84 tokens