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 IdoCohen560/claude-unity-game-studio --skill team-qagit clone --depth 1 https://github.com/IdoCohen560/claude-unity-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/idocohen560/claude-unity-game-studio/team-qa)<a href="https://agentmods.dev/skills/idocohen560/claude-unity-game-studio/team-qa"><img src="https://agentmods.dev/badge/skills/idocohen560/claude-unity-game-studio/team-qa/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/idocohen560/claude-unity-game-studio/team-qa"><img src="https://agentmods.dev/badge/skills/idocohen560/claude-unity-game-studio/team-qa.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.02405 |
| Opus 5 | $0.00036 | $0.01203 |
| Sonnet 5 | $0.00015 | $0.00481 |
| Haiku 4.5 | $0.00007 | $0.00241 |
Grade A, and why
team-qa 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 5d 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.
This is a copy
84% identical to team-qa — 42 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 — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When this skill is invoked, orchestrate the QA team through a structured testing cycle.
Decision Points: At each phase transition, use AskUserQuestion to present
the user with the subagent's proposals as selectable options. Write the agent's
full analysis in conversation, then capture the decision with concise labels.
The user must approve before moving to the next phase.
Team Composition
- qa-lead — QA strategy, test plan generation, story classification, sign-off report
- qa-tester — Test case writing, bug report writing, manual QA documentation
How to Delegate
Use the Task tool to spawn each team member as a subagent:
subagent_type: qa-lead— Strategy, planning, classification, sign-offsubagent_type: qa-tester— Test case writing and bug report writing
Always provide full context in each agent's prompt (story file paths, QA plan path, scope constraints). Launch independent qa-tester tasks in parallel where possible (e.g., multiple stories in Phase 5 can be scaffolded simultaneously).
Pipeline
Phase 1: Load Context
Before doing anything else, gather the full scope:
-
Detect the current sprint or feature scope from the argument:
- If argument is a sprint identifier (e.g.,
sprint-03): read all story files inproduction/sprints/[sprint]/ - If argument is
feature: [system-name]: glob story files tagged for that system - If no argument: read
production/session-state/active.mdandproduction/sprint-status.yaml(if present) to infer the active sprint
- If argument is a sprint identifier (e.g.,
-
Read
production/stage.txtto confirm the current project phase. -
Count stories found and report to the user:
"QA cycle starting for [sprint/feature]. Found [N] stories. Current stage: [stage]. Ready to begin QA strategy?"
Phase 2: QA Strategy (qa-lead)
Spawn qa-lead via Task to review all in-scope stories and produce a QA strategy.
Prompt the qa-lead to:
- Read each story file
- Classify each story by type: Logic / Integration / Visual/Feel / UI / Config/Data
- Identify which stories require automated test evidence vs. manual QA
- Flag any stories with missing acceptance criteria or missing test evidence that would block QA
- Estimate manual QA effort (number of test sessions needed)
- Check
tests/smoke/for smoke test scenarios; for each, assess whether it can be verified given the current build. Produce a smoke check verdict: PASS / PASS WITH WARNINGS [list] / FAIL [list of failures] - Produce a strategy summary table and smoke check result:
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.
- 5d ago First seen · 223 lines · 73 tokens per session scan A aa37177cb04f
team-qa is a skill published in the GitHub repository IdoCohen560/claude-unity-game-studio (18 stars, last pushed 2mo ago), licensed MIT. It adds 73 tokens to every session and 2,405 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 84% identical to team-qa, differing in 42 lines, and is treated as a copy.
Other skills, from other repositories
plan-qa
Post-implementation QA planning — independent of /review (the developer chooses whether to run them sequentially or in parallel), only when the change has a running surface worth driving. Interviews the developer to turn the specs and the diff into an executable QA specification (specs/qa/QA- - .md) that /execute-qa…
execute-qa
Executes a QA specification (specs/qa/QA- - .md) written by /plan-qa: drives every step with the plan's drivers, verifies each Expected line mechanically ([assert]) or by evidence-backed judgment against the plan's written criterion ([judge]), pauses at named operator handoffs, and writes the results artifact…
generate-tasks
Phase 3 of 5 — slices the ARCH doc into verification-ready task specs (tdd/test-after/ui/checklist), emitted as a separate TASKS- - .md file alongside ARCH for the implement skill. Use only when the user asks to run Phase 3 or generate tasks from an ARCH doc — never trigger automatically.
mvp-readiness
Runs a structured MVP quality-gate audit covering stability, security, logging, docs, and implementation integrity. Reports pass/fail with evidence.
requirements-generator
Generates structured requirements documents with functional and non-functional requirements, Gherkin acceptance criteria, edge cases, and out-of-scope items.
test-writer
Generates comprehensive unit and integration tests for a given file or function, auto-detecting the project test framework and matching existing test style.