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 bullish0x/GameStudio --skill qa-plangit clone --depth 1 https://github.com/bullish0x/GameStudioWrote 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/bullish0x/gamestudio/qa-plan)<a href="https://agentmods.dev/skills/bullish0x/gamestudio/qa-plan"><img src="https://agentmods.dev/badge/skills/bullish0x/gamestudio/qa-plan/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/bullish0x/gamestudio/qa-plan"><img src="https://agentmods.dev/badge/skills/bullish0x/gamestudio/qa-plan.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.00073 | $0.02928 |
| Opus 5 | $0.00036 | $0.01464 |
| Sonnet 5 | $0.00015 | $0.00586 |
| Haiku 4.5 | $0.00007 | $0.00293 |
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 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.
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 --> This is a copy
95% identical to qa-plan — 3 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 278 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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: $ARGUMENTS (blank = ask user via AskUserQuestion)
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
AskUserQuestion:- "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:
- Story title and story ID (from filename or header)
- Story Type field (if present in the file header — e.g.,
Type: Logic) - Acceptance criteria — the complete numbered/bulleted list
- Implementation files — listed under "Files to Create / Modify" or similar
- Engine notes — any engine API warnings or version-specific notes
- GDD reference — the GDD path(s) cited
- ADR reference — the ADR(s) cited
- Estimate — hours or story points if present
- Dependencies — other stories this one depends on
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 · 278 lines · 73 tokens per session scan C 60a0eeed8ecd
qa-plan is a skill published in the GitHub repository bullish0x/GameStudio (12 stars, last pushed 3mo ago), licensed MIT. It adds 73 tokens to every session and 2,928 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it C with 1 finding (hidden instructions). It is 95% identical to qa-plan, differing in 3 lines, and is treated as a copy.
Other skills, from other repositories
unity-agent-workflows
Use for AI-assisted Unity work that needs live repo discovery, project-derived routing, runtime-owner proof, runtime-visible output hard stops, runtime numeric proof for repeated visible-output failures, state-step guards, multi-agent scope ownership, modular C#/asmdef safety, UI/scene/visual asset gates, data-first…
testing-bgs-modpack
A checklist and decision guide for checking a newly installed batch of Bethesda Game Studios game modifications before accepting it as ready.
agent-eval
Use when measuring whether an LLM or agent system actually got better and gating merges on it: golden sets, fixing an inflated LLM-as-judge, scoring RAG (faithfulness, contextual recall) or agent trajectories (tool correctness, completion), or picking an eval framework. NOT building the agent loop, tools or RAG…
accessibility-a11y
WCAG 2.2 compliance, ARIA patterns, keyboard navigation, screen readers, automated testing.
game-development
Game development with Unity, Unreal Engine, and Godot. Use when building games, implementing game mechanics, physics, AI, or working with game engines.
ar-vr-xr
AR/VR/XR development with Unity XR, WebXR, ARKit, ARCore, Meta Quest SDK, and spatial computing. Use when building augmented reality, virtual reality, mixed reality applications, or spatial experiences.