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 jeremylongworth-source/AgentSkills --skill game-playtesting-usabilitygit clone --depth 1 https://github.com/jeremylongworth-source/AgentSkillsWrote 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/jeremylongworth-source/agentskills/game-playtesting-usability)<a href="https://agentmods.dev/skills/jeremylongworth-source/agentskills/game-playtesting-usability"><img src="https://agentmods.dev/badge/skills/jeremylongworth-source/agentskills/game-playtesting-usability/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/jeremylongworth-source/agentskills/game-playtesting-usability"><img src="https://agentmods.dev/badge/skills/jeremylongworth-source/agentskills/game-playtesting-usability.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.00076 | $0.00408 |
| Opus 5.5 | $0.00030 | $0.00163 |
| Sonnet 5.5 | $0.00015 | $0.00082 |
| Haiku 4.5 | $0.00008 | $0.00041 |
Grade A, and why
game-playtesting-usability 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 1mo 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
Game Playtesting Usability
Core Workflow
- Define the design question: comprehension, controls, difficulty, fun, pacing, balance, retention, onboarding, UI clarity, accessibility, or market appeal.
- Select playtest type: internal smoke test, moderated usability test, unmoderated remote playtest, telemetry test, balance test, first-time-user test, longitudinal test, or public demo feedback.
- Recruit players that match the target audience and note bias.
- Create tasks, observation prompts, success criteria, and data capture before testing.
- Observe behavior before asking opinions. Record confusion, hesitation, repeated failure, emotion, workaround, and drop-off.
- Synthesize issues by severity, frequency, player segment, root cause, and design implication.
- Convert findings into concrete design changes and retest criteria.
Playtest Principles
- Do not coach unless the test explicitly allows help.
- Separate bugs, usability problems, balance problems, and preference feedback.
- Watch what players do, not only what they say.
- Test early prototypes for comprehension and later builds for tuning, retention, and polish.
- Treat small samples as directional; use telemetry or larger samples for stronger claims.
Deliverable Shape
For playtesting work, provide:
- Research question and build/context
- Participant criteria
- Test plan and tasks
- Data capture plan
- Findings by severity and evidence
- Recommended changes
- Retest plan
References
- Read
references/game-playtesting-checklist.mdwhen planning, running, or synthesizing game playtests.
What ships with it
2 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.
- 1mo ago First seen · 42 lines · 76 tokens per session scan A fe9641b943bf
game-playtesting-usability is a skill published in the GitHub repository jeremylongworth-source/AgentSkills (1 stars, last pushed 17d ago), licensed MIT. It adds 76 tokens to every session and 408 once invoked, about $0.0003 per session on Opus 5.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
game-visual-self-review
Use when you are about to hand off a change a player can see - the exact steps to look at it running (web game in the browser at two viewports plus a seeded Playwright smoke run for input and console errors; engine games through a headless frame capture), the checklist, and how to report what could not be observed.
godot-testing
Use when writing or running Godot tests - gdUnit4 or GUT (whichever the repo has), unit tests on typed GDScript classes, scene runners for frames, physics, input and signals, headless CLI with --import first, reports and exit codes, and C# tests via gdUnit4Net or plain dotnet test.
unity-testing
Use when writing or running Unity tests - Unity Test Framework EditMode vs PlayMode, test assembly definitions, testing plain C# and ScriptableObjects, PlayMode scene/physics/input tests, batchmode CLI with result XML, coverage, and the dotnet test fallback when no editor is installed.
web-game-performance-and-testing
Use when working on any browser game (Phaser, PixiJS, three.js, Babylon.js, PlayCanvas, Excalibur, KAPLAY) - requestAnimationFrame with clamped delta and visibility pause, zero-allocation frame loops, measuring in DevTools, bundle and asset size budgets, Vitest with seeded RNG and injected time, and a seeded…
unity-yaml-format
Inspect, explain, diff, and carefully edit Unity text-serialized files such as .unity, .prefab, .asset, and related YAML-based project files. Use when mapping class IDs and fileIDs, tracing object references, reviewing merge conflicts, or making minimal safe edits to existing UnityYAML documents.
tester
Run end-to-end web quality audits with Playwright and Lighthouse using existing project scripts first. Use when the user says /tester, e2e test, smoke test, Playwright audit, Lighthouse audit, performance audit, accessibility audit, dark mode audit, mobile audit, or asks for 100/100 Lighthouse improvement guidance.