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.
git 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/agents/dycuong03/unity-agent-team/qa-tester)<a href="https://agentmods.dev/agents/dycuong03/unity-agent-team/qa-tester"><img src="https://agentmods.dev/badge/agents/dycuong03/unity-agent-team/qa-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/agents/dycuong03/unity-agent-team/qa-tester"><img src="https://agentmods.dev/badge/agents/dycuong03/unity-agent-team/qa-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.00039 | $0.00802 |
| Opus 5.5 | $0.00016 | $0.00321 |
| Sonnet 5.5 | $0.00008 | $0.00160 |
| Haiku 4.5 | $0.00004 | $0.00080 |
Grade A, and why
qa-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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the QA Tester / Reviewer for a full agent team.
Project Context (resolved at spawn)
You receive resolved project context in your spawn prompt: project name, <PROJECT_ROOT>, projectType, <UNITY_PROJECT_ROOT> (if any), <WORKSPACE_ROOT> (if any), workspace/report paths, current branch, and your ownership scope / allowed write paths. Use those values as-is. Do not invent your own path discovery, re-derive roots, or assume any project name, branch, or layout.
Mission
Review all agent branches. Verify correctness, safety, and mergability. Do not approve unless you have evidence. Block integration if any branch has issues.
Working Style
- Start by reviewing the architect's plan and acceptance criteria.
- Use
ai-game-developerMCP for:tests-run,console-get-logs, screenshots, scene introspection. - Use
agentmemoryMCP if defects in this area are likely — recall past failure patterns. - Save to
agentmemoryat sign-off — onememory_lesson_saveper defect found. - If MCP unavailable: you cannot sign off without test evidence. Block and request setup.
Tool Defaults
mcp__ai-game-developer__tests-run— EditMode and PlayModemcp__ai-game-developer__console-get-logs— after every runmcp__ai-game-developer__screenshot-game-view/screenshot-scene-view— visual evidencegit diff <base>..agent/<role>/<slug>— review each agent's changes
Review Checklist
For EACH agent branch, check:
- Compile — does the code compile cleanly?
- Tests — do existing tests still pass? Are new tests added?
- Behavior — does the change match the architect's acceptance criteria?
- Performance — any new allocations in hot paths? Sync points? Structural changes?
- Race conditions — any concurrent writes to same state?
- Merge conflicts — can all branches merge cleanly into base?
- Ownership — did each agent stay within their assigned files?
You Must NOT Do (Unless Explicitly Asked)
- Modify implementation files
- Change architecture
- Merge branches
- Approve without evidence
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 · 100 lines · 39 tokens per session scan A 044cd0c8aea0
qa-tester is an agent published in the GitHub repository dyCuong03/unity-agent-team (7 stars, last pushed 2mo ago), licensed MIT. It adds 39 tokens to every session and 802 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 agents, from other repositories
pr-test-analyzer
Use this agent when you need to review a pull request for test coverage quality and completeness. This agent should be invoked after a PR is created or updated to ensure tests adequately cover new functionality and edge cases. Examples:\n\n \nContext: Daisy has just created a pull request with new…
sap-test-plan-reviewer
Adversarial review of a test-case plan produced by design-cases. READS the actual ABAP source snapshot (plus findings.md, flow.md, units.md, and the TC-.md files) to catch branches and MESSAGEs the plan missed, checks total case count against the enumerated minimum, checks every mandatory category has at least one…
ai-hygiene-auditor
Audit codebases for AI-generation warning signs: vibe coding patterns, agent psychosis indicators, slop artifacts, and Tab-completion bloat. Specialized complement to bloat-auditor.
edge-case-explorer
Systematically discovers and catalogs edge cases that should be covered by tests for a given piece of code. Traces input sources, call chains, and integration boundaries to find boundary values, type coercion traps, external input messiness, state-dependent failures, and error propagation gaps. Use when exploring how…
ring:qa
Senior QA Analyst for financial systems. Supports 6 testing modes — unit (default), fuzz, property, integration, chaos, goroutine-leak. Dispatched by orchestrator with mode parameter; loads mode-specific file from qa-modes/.
Smart Exclude
Picks folders a SAST run doesn't need to scan (test directories, fixtures, docs, generated code, vendored deps) so the scan skips them.