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 striderZA/OpenCodeGameStudios --skill qa-plangit clone --depth 1 https://github.com/striderZA/OpenCodeGameStudiosWrote 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/striderza/opencodegamestudios/qa-plan)<a href="https://agentmods.dev/skills/striderza/opencodegamestudios/qa-plan"><img src="https://agentmods.dev/badge/skills/striderza/opencodegamestudios/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/striderza/opencodegamestudios/qa-plan"><img src="https://agentmods.dev/badge/skills/striderza/opencodegamestudios/qa-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 249 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.02556 |
| Opus 5.5 | $0.00029 | $0.01022 |
| Sonnet 5.5 | $0.00015 | $0.00511 |
| Haiku 4.5 | $0.00007 | $0.00256 |
Grade A, and why
qa-plan 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- qa-plan — 95% identical, 10 lines differ
How it starts
The opening of the file, as written. The whole thing — 260 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 question)
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
question:- "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.
- 1mo ago First seen · 260 lines · 73 tokens per session scan A fea238b6e8e3
qa-plan is a skill published in the GitHub repository striderZA/OpenCodeGameStudios (99 stars, last pushed 13d ago), licensed MIT. It adds 73 tokens to every session and 2,556 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
team-combat
Orchestrate the combat team: coordinates game-designer, gameplay-programmer, ai-programmer, technical-artist, sound-designer, and qa-tester to design, implement, and validate a combat feature end-to-end.
team-polish
Orchestrate the polish team: coordinates performance-analyst, technical-artist, sound-designer, and qa-tester to optimize, polish, and harden a feature or area for release quality.
procgen-design
Design procedural content systems with seeds, constraints, and validation gates so generated output stays fun and shippable.
animation-state-patterns
Structure animation state, blending, events, and sync so authored motion remains reliable under gameplay pressure.
qa-test-matrix
Build a coverage matrix that shows what must be tested, on which configurations, and at what milestone confidence level.
godot-testing
Choose effective automated and manual test layers for Godot features without overcomplicating the project.