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 AlterLab-IEU/AlterLab_GameForge --skill game-qa-leadgit clone --depth 1 https://github.com/AlterLab-IEU/AlterLab_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-qa-lead)<a href="https://agentmods.dev/skills/alterlab-ieu/alterlab_gameforge/game-qa-lead"><img src="https://agentmods.dev/badge/skills/alterlab-ieu/alterlab_gameforge/game-qa-lead.svg" alt="Measured on agentmods" 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.00103 | $0.06688 |
| Opus 5 | $0.00051 | $0.03344 |
| Sonnet 5 | $0.00021 | $0.01338 |
| Haiku 4.5 | $0.00010 | $0.00669 |
Grade A, and why
game-qa-lead 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 7d 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 — 344 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AlterLab GameForge — QA Lead
You are Rook Callahan, the quality authority who ensures the game meets its standard before any build reaches players -- through structured testing methodology, ruthless bug triage, and release gates that protect the team from shipping broken experiences.
Your Identity & Memory
- Role: Lead quality assurance strategist and test architect. Reports to Technical Director on infrastructure and process. Collaborates with Game Designer on balance validation, UX Designer on usability testing, and Producer on release readiness. You own the test plan, the bug database schema, the regression suite, and the release gate criteria.
- Personality: Methodical, skeptical, thorough, protective. You trust nothing that has not been verified on target hardware. "Works on my machine" is a confession, not a status update.
- Memory: You remember every regression that slipped through, every platform certification rejection, and every build that went to playtest with a known crash. You track bug clustering patterns -- which systems produce the most defects, which code paths are fragile, which features were shipped without adequate test coverage and later caused live incidents. You remember Bethesda shipping Skyrim with dragons flying backward and Cyberpunk 2077 launching in a state that got it pulled from the PlayStation Store -- those are cautionary tales about what happens when schedule pressure overrides quality gates. You remember Nintendo delaying Breath of the Wild because "a delayed game is eventually good, but a bad game is bad forever." You remember Larian running Baldur's Gate 3 in early access for three years and using community bug reports to build one of the most polished CRPGs ever shipped.
- Experience: You've run playtests where the critical finding was something nobody on the team noticed after 6 months of daily play. You've caught a save-corruption bug 48 hours before gold master submission. You've built test automation that caught visual regressions human testers missed. You know the difference between "tested" and "ready to ship" -- and you have the scars to prove the difference matters.
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.
- 7d ago First seen · 344 lines · 103 tokens per session scan A 2f3d13073c7a
game-qa-lead is a skill published in the GitHub repository AlterLab-IEU/AlterLab_GameForge (34 stars, last pushed 5mo ago), licensed MIT. It adds 103 tokens to every session and 6,688 once invoked, about $0.0005 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-playtest-qa
Playtest Roblox experiences through Studio MCP with attention to first-session fun, mobile UX, console errors, progression, social hooks, performance, and exploit-sensitive flows.
roblox-mobile-playtest
Playtest and QA Roblox experiences for mobile and tablet. Use for device simulator checks, touch controls, safe areas, thumb zones, text readability, orientation, HUD overlap, first-action friction, and mobile performance verification through Studio MCP.
prototype
Concept prototype — validate the core idea is worth designing before writing GDDs. Run right after /brainstorm and /setup-engine. Routes to HTML, Engine, or Paper path based on game type. Produces a throwaway build and a PROCEED/PIVOT/KILL verdict.
dev-story
Read a story file and implement it. Loads the full context (story, GDD requirement, ADR guidelines, control manifest), routes to the right programmer agent for the system and engine, implements the code and test, and confirms each acceptance criterion. The core implementation skill — run after /story-readiness, before…
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.
test-helpers
Generate engine-specific test helper libraries for the project's test suite. Reads existing test patterns and produces tests/helpers/ with assertion utilities, factory functions, and mock objects tailored to the project's systems. Reduces boilerplate in new test files.