Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add AlterLab-IEU/AlterLab_GameForge/plugin install gameforgeWrote 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/alterlab-ieu/alterlab_gameforge/game-playtest)<a href="https://agentmods.dev/skills/alterlab-ieu/alterlab_gameforge/game-playtest"><img src="https://agentmods.dev/badge/skills/alterlab-ieu/alterlab_gameforge/game-playtest/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/alterlab-ieu/alterlab_gameforge/game-playtest"><img src="https://agentmods.dev/badge/skills/alterlab-ieu/alterlab_gameforge/game-playtest.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.00082 | $0.04603 |
| Opus 5.5 | $0.00033 | $0.01841 |
| Sonnet 5.5 | $0.00016 | $0.00921 |
| Haiku 4.5 | $0.00008 | $0.00460 |
Grade A, and why
game-playtest 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 today.
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 — 339 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AlterLab GameForge -- Structured Playtest
Playtesting is not asking players whether they had fun. It is disciplined observation of what players do, so you can see where the design communicates and where it fails. What players say is useful context; what their hands do is evidence. This workflow turns sessions with real people into findings the team can act on, and keeps the newer tools (AI playtest agents, feedback summarizers, browser builds) in their proper place: useful supplements, never the primary instrument.
Purpose & Triggers
Use this workflow when:
- A build is ready for outside eyes and you need structured findings, not reactions.
- A specific design question needs an answer: "Do players understand crafting?" rather than "Is it good?"
- Onboarding needs validation: can a new player learn the core verb without a tutorial?
- The difficulty curve needs checking against real players, not the team's muscle memory.
- You have raw notes, recordings, survey exports or Discord/Steam feedback to analyze.
- You want a repeatable remote or browser-based playtest setup as a solo developer.
Do NOT use this workflow when:
| Need | Route to |
|---|---|
| Testing one raw mechanic in isolation | game-prototype |
| Finding bugs, smoke tests, automated or AI-agent QA runs | game-qa-lead |
| Tuning numbers, simulations, win rates | game-balance-check |
| Heuristic usability review or onboarding redesign | game-ux-designer |
| Testing with disabled players, accommodation checks | game-accessibility-specialist (co-run) |
| Building the telemetry pipeline and dashboards | game-analytics-setup |
| Market validation, wishlist tests, marketing quotes | game-market-research |
| Publishing a public web build to portals | game-web-publish |
If the build crashes or softlocks on the path you want to test, stop: run the playtest-build gate
in game-qa-lead first. Testers who spend the session hitting bugs give you bug reports, not
design findings.
Inputs I Read First
.gameforge/project.json(phase, pillars, engine), the GDD sections for the feature under test indesign/, previous reports intests/playtests/, andproduction/session-state/active.md.- Then ask up to three AskUserQuestion items, each with a default:
- Goal: first impression (default for early builds), targeted feature, difficulty curve, full playthrough.
- Format: remote moderated over a call (default for solo devs), in person, remote unmoderated (browser build or Steam Playtest).
- Tester pool: friends of friends, the game's Discord, strangers (Steam Playtest, itch.io restricted page). Default: people who have never seen the game and match the target audience.
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.
- today Changed · -40 lines · -15 tokens per session f4ef5fc177b0
- 2mo ago First seen · 379 lines · 97 tokens per session scan A b76d7c107c5a
game-playtest is a skill published in the GitHub repository AlterLab-IEU/AlterLab_GameForge (52 stars, last pushed yesterday), licensed MIT. It adds 82 tokens to every session and 4,603 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-08-30.
game-playtest compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| game-playtestAlterLab-IEU/AlterLab_GameForge | Skill | 52 | yesterday | MIT | A | 82 | Claude Code |
| playtest-reportDonchitos/Claude-Code-Game-Studios | Skill | 36k | 18d ago | MIT | A | 20 | Claude Code |
| godot-signals-groupsgamedev-skills/awesome-gamedev-agent-skills | Skill | 6.9k | 9d ago | Apache-2.0 | A | 95 | Claude Code |
| scenario-unreal-gameplayscenario-labs/skills | Skill | 3.2k | yesterday | MIT | A | 121 | Claude Code |
| motionOpenDCAI/GameFactory-3A | Skill | 1.0k | 8d ago | Apache-2.0 | A | 0 | Claude Code, Codex |
| unity-addressablesBesty0728/Unity-Skills | Skill | 1.9k | yesterday | MIT | A | 25 | Claude Code, Codex |
| unity-manual-componentBesty0728/Unity-Skills | Skill | 1.9k | yesterday | MIT | A | 36 | Claude Code, Codex |