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 agentmods add skills/frabcd/codex-ai-game-studio/qa-plannpx skills add frabcd/codex-ai-game-studio --skill qa-plangit clone --depth 1 https://github.com/frabcd/codex-ai-game-studioWrote 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/frabcd/codex-ai-game-studio/qa-plan)<a href="https://agentmods.dev/skills/frabcd/codex-ai-game-studio/qa-plan"><img src="https://agentmods.dev/badge/skills/frabcd/codex-ai-game-studio/qa-plan.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.00073 | $0.03057 |
| Opus 5 | $0.00036 | $0.01528 |
| Sonnet 5 | $0.00015 | $0.00611 |
| Haiku 4.5 | $0.00007 | $0.00306 |
Grade C, and why
qa-plan scanned grade C with 1 finding 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 6d 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
<!-- QA-PLAN: [date] | System: [system/sprint identifier] | Plan written: production/qa/qa-plan-[identifier]-[date].md --> How it starts
The opening of the file, as written. The whole thing — 280 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Port provenance: adapted from the pinned upstream source at
984023ddac0d5e27624f2baacde6105e45de375funder MIT; see the repository parity ledger for the exact path and blob.
QA Plan
This skill generates a structured QA plan for a sprint, feature, or individual story. It reads all in-scope story files and their referenced GDDs, classifies each story by test type, and produces a plan that tells developers exactly what to automate, what to verify manually, what the smoke test scope is, and when to bring in a playtester.
Run this before a sprint begins so the team knows upfront what testing work is required. A test plan written after implementation is a post-mortem, not a plan.
Output: production/qa/qa-plan-[sprint-slug]-[date].md
Phase 1: Parse Scope
Argument: the invocation arguments (blank = ask user via the available user-input mechanism)
Determine scope from the argument:
sprint— read the most recent file inproduction/sprints/, extract every story file path referenced. Ifproduction/sprint-status.yamlexists, use it as the primary story list and fall back to the sprint plan for story metadata.feature: [system-name]— globproduction/epics/*/story-*.md, filter to stories whose file path or title contains the system name. Also check the epic index file (EPIC.md) in that system's directory.story: [path]— validate that the path exists and load that single file.- No argument — use
the available user-input mechanism:- "What is the scope for this QA plan?"
- Options: "Current sprint", "Specific feature (enter system name)", "Specific story (enter path)", "Full epic"
After resolving scope, report: "Building QA plan for [N] stories in [scope]."
If a story file path is referenced but the file does not exist, note it as MISSING and continue with the remaining stories. Do not fail the entire plan for one missing file.
Phase 2: Load Inputs
For each in-scope story file, read the full file and extract:
What ships with it
1 file 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.
- 6d ago First seen · 280 lines · 73 tokens per session scan C 93bfe69a93ef
qa-plan is a skill published in the GitHub repository frabcd/codex-ai-game-studio (9 stars, last pushed 5d ago), licensed MIT. It adds 73 tokens to every session and 3,057 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
game-build
Build a risk-matched whitebox or the approved production game for its target runtime. Turn GAMEDESIGN, and ARTDIRECTION when production begins, into a minimal BUILDBRIEF and a runnable candidate that can be iterated with replayable evidence. Use for prototype the riskiest design question, implement the approved game…
game-concept
Design game concepts from a novel. From SOURCEBIBLE and PRODUCTBRIEF, generate three genuinely different directions on the dimensions still unlocked, then pick the most worthwhile playable prototype using hard vetoes and explicit trade-offs. Use for what game should this novel become, compare game concepts, choose a…
game-qa
Verify a game with evidence on its selected target runtime. Launch the actual build and prove real rendering, input, the core loop, at least one designed outcome, restart, and explicit limitations without dressing subjective fun up as a certain verdict. Use for test a generated game, QA a game build, check whether the…
3d_scene
Choose how to build a 3dscene asset. Do not default to one pipeline for every task: what the user specified about the scene's appearance matters more than the scene type, and generative reconstruction is the least stable route here.
cinematic-cutscene
Use when generating a non-interactive cutscene clip — opening scene, story beat, character intro, ending. Locks the look with a reference image, image-to-videos a 5-10s shot, optionally adds TTS dialogue, and wires it as a VideoStreamPlayer that fades in/out. Trigger on "cutscene", "intro cinematic", "opening scene"…
lightning
Use when authoring a lightning bolt visual effect — procedural jagged path drawn via ImmediateMesh, glow shader, sparks at endpoints, screen shake. Trigger on "lightning bolt", "chain lightning", "electric attack", "tesla coil", "shock spell", "thunderbolt", "energy beam".