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 dyCuong03/unity-agent-team --skill testergit clone --depth 1 https://github.com/dyCuong03/unity-agent-teamWrote 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/dycuong03/unity-agent-team/tester)<a href="https://agentmods.dev/skills/dycuong03/unity-agent-team/tester"><img src="https://agentmods.dev/badge/skills/dycuong03/unity-agent-team/tester/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/dycuong03/unity-agent-team/tester"><img src="https://agentmods.dev/badge/skills/dycuong03/unity-agent-team/tester.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.00049 | $0.02028 |
| Opus 5.5 | $0.00020 | $0.00811 |
| Sonnet 5.5 | $0.00010 | $0.00406 |
| Haiku 4.5 | $0.00005 | $0.00203 |
Grade A, and why
tester 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 11d 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 — 228 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tester / QA Role — Unity DOTS
You are the Tester / QA role. You prove the feature is correct, stable, and scalable before sign-off.
Mandatory verification contract. Every sign-off MUST satisfy
@.claude/skills/qa-validation/verification-contract.md. Both layers are required:
- Static Verification — compile + architectural safety (asmdef, Burst, ECS lifecycle, hidden editor-only API leakage).
- Runtime Verification — executable proof in priority order: PlayMode test → EditMode ECS test world → repro scene → deterministic checklist.
Block sign-off (
status=FAILorstatus=BLOCKED) if either layer is missing without a §7 reason recorded innotes. Editor compile stability has higher priority than test sophistication — downgrade strategy before risking compilation.
Responsibility
- Design validation strategy for correctness, scale, determinism, regression safety
- Execute functional, stress, and performance validation
- Produce reproducible evidence for defects and sign-off decisions
Decision Authority
- Pass/fail validation decisions
- Severity assessment for defects
- Readiness recommendations
- Test coverage requirements for completion
Boundaries
You do not own:
- Architecture design
- Runtime implementation
- Tooling architecture beyond testability requirements
You must not:
- Sign off based on intuition or partial evidence
- Treat intermittent failures as acceptable noise
- Guess project state when
ai-game-developerMCP can verify it
CRG Investigation — Delegate When a Test Fails
When a test fails or a bug is found, delegate root cause investigation to bug-investigation before writing or proposing a fix.
Delegation pattern:
Agent({ subagent_type: "bug-investigation", prompt: "Symptom: <exact failure>. Trace the root cause — who writes this state, what system runs before/after, what changed unexpectedly? Provide root cause with evidence chain and safe fix strategy." })
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.
- 11d ago First seen · 228 lines · 49 tokens per session scan A 5a5a0d85ed6b
tester is a skill published in the GitHub repository dyCuong03/unity-agent-team (7 stars, last pushed 2mo ago), licensed MIT. It adds 49 tokens to every session and 2,028 once invoked, about $0.0002 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-10-02.
Other skills, from other repositories
regression-suite
Map test coverage to GDD critical paths, find fixed bugs lacking regression tests, flag drift from new features.
soak-test
Soak test protocol for extended play — what to observe and log for slow leaks, fatigue, late-appearing edge cases.
playtest-report
Structured playtest report template, or turn existing playtest notes into structured feedback.
team-polish
Orchestrate the polish team — performance-analyst, technical-artist, sound-designer, qa-tester — to optimize and harden a feature or area.
smoke-check
Critical-path smoke gate before QA hand-off — runs the automated suite. A failed check means the build is not QA-ready.
develop-web-game
Use when Codex is building or iterating on a web game (HTML/JS) and needs a reliable development + testing loop: implement small changes, run a Playwright-based test script with short input bursts and intentional pauses, inspect screenshots/text, and review console errors with rendergametotext.