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 nonlooped/roblox-suite --skill roblox-testinggit clone --depth 1 https://github.com/nonlooped/roblox-suiteWrote 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/nonlooped/roblox-suite/roblox-testing)<a href="https://agentmods.dev/skills/nonlooped/roblox-suite/roblox-testing"><img src="https://agentmods.dev/badge/skills/nonlooped/roblox-suite/roblox-testing.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00080 | $0.02876 |
| Opus 5 | $0.00040 | $0.01438 |
| Sonnet 5 | $0.00016 | $0.00575 |
| Haiku 4.5 | $0.00008 | $0.00288 |
Grade A, and why
roblox-testing 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 8d 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 — 358 lines — stays where its author put it; the contents beside it link to each section on GitHub.
roblox-testing
Official sources (always check these for the latest):
- https://create.roblox.com/docs/en-us/studio/developer-console
- https://create.roblox.com/docs/en-us/performance-optimization/identify
- https://create.roblox.com/docs/en-us/performance-optimization/microprofiler
- https://create.roblox.com/docs/en-us/performance-optimization/scene-analysis
- https://create.roblox.com/docs/en-us/studio/optimization/memory-usage
- https://create.roblox.com/docs/en-us/studio/optimization/scriptprofiler
This skill is about finding and fixing problems, not just writing code. It focuses on the tools and habits that separate working experiences from broken ones.
When to use this skill
Activate when:
- Something is not behaving as expected (scripts, UI, physics, data, networking).
- Frame rate, memory, or server heartbeat is degrading.
- Setting up unit tests or reproducible test cases.
- Trying to isolate whether a bug is on the client or server.
- Debugging a live issue using the Developer Console.
Cross-reference:
- roblox-core/SKILL.md for services and script contexts.
- roblox-networking/SKILL.md for debugging remote flows and network ownership.
- roblox-datastores/SKILL.md for DataStore retry patterns and debugging data store errors.
- roblox-physics/SKILL.md for debugging physics ownership and sleep.
- roblox-npcs/SKILL.md for debugging NPC behavior.
The debugging mindset
- Reproduce it. If you can't reproduce it, you can't fix it.
- Isolate it. Remove systems until the bug disappears; the last thing removed is the cause.
- Measure it. Use tools instead of guessing.
- Fix one thing at a time. Verify the fix and add a regression test if possible.
- Log defensively. Good logs make future debugging faster.
Logging discipline
Use print, warn, and error deliberately:
printfor normal diagnostics.warnfor recoverable problems you should notice.errorfor programming errors that should stop execution.
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 358 lines · 80 tokens per session scan A 427b8e61b41e
roblox-testing is a skill published in the GitHub repository nonlooped/roblox-suite (14 stars, last pushed 4d ago), licensed MIT. It adds 80 tokens to every session and 2,876 once invoked, about $0.0004 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-30.
Other skills, from other repositories
roblox-validation-and-qa
Use when deciding whether a change in a Roblox project counts as tested, verified, or done, before claiming PASS or "works", when writing or running Jest Lua unit specs (.spec.luau), adding a tests/scenarios/.md playtest scenario, adding a UI Labs storybook story, moving a board card into or out of the Testing lane…
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.
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…
gm-verify
Mechanical verification of the built game: headless build, unit tests, lint, static checks. Explicit invocation only — use /gm-verify.
roblox-engineer
!cat skills/shared/game-visual-foundations.md 2>/dev/null || echo "=== Visual Foundations not loaded ===" !cat skills/shared/protocols/ux-protocol.md 2>/dev/null || true !cat skills/shared/protocols/game-test-protocol.md 2>/dev/null || true !cat skills/shared/protocols/quality-gate.md 2>/dev/null || true !cat…
gut-test-writer
Write GUT (Godot Unit Test) tests for components, scenes, autoloads. Generates test structure, beforeeach/aftereach setup, signal watching, parameterized tests, headless run config, and CI integration. Use after implementing a feature or fixing a bug.