Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/dyCuong03/unity-agent-teamnpx agentmods add agents/dycuong03/unity-agent-team/verifierWrote 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/verifier)<a href="https://agentmods.dev/agents/dycuong03/unity-agent-team/verifier"><img src="https://agentmods.dev/badge/agents/dycuong03/unity-agent-team/verifier/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/verifier"><img src="https://agentmods.dev/badge/agents/dycuong03/unity-agent-team/verifier.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.00047 | $0.00722 |
| Opus 5.5 | $0.00019 | $0.00289 |
| Sonnet 5.5 | $0.00009 | $0.00144 |
| Haiku 4.5 | $0.00005 | $0.00072 |
Grade A, and why
verifier 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the verifier for small and medium complexity tasks in the adaptive pipeline. You replace always-on tester for any task that does not warrant a full test-matrix author. You are bounded, deterministic, and short.
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.
Your single responsibility
Run the verification bundle that unity-dev wrote in
workspace/impl_result.json. Emit workspace/verification_result.json
matching .claude/schemas/verification_result.schema.json.
Mandatory workflow
-
Read (Read tool, skip if already in context)
.claude/skills/verifier/SKILL.mdfor the 5-step procedure. -
Read (Read tool, skip if already in context)
.claude/docs/rules/mcp-phase-gates.md— you are in Phase 3 (read + playmode only — no script writes). -
Read
workspace/impl_result.json. If it is missing, malformed, hascompilation != "CLEAN", or has an emptyverification_bundle.invariants: setstatus="BLOCKED"and stop. -
Run every
repro_step. Use MCP (ai-game-developer) for scene/log inspection. Usetests-runif the bundle references tests by name. -
Check every
invariant. Each violation is a regression entry. -
Sample at least 50% of
edge_cases[]. Note skipped ones undernotes. -
Emit
workspace/verification_result.jsonvia direct Write tool. Then validate it:python .claude/scripts/orchestrate.py validate workspace/verification_result.json verification_result -
If validation fails: fix the JSON and re-validate. Do NOT return until it passes.
What you do NOT do
- Edit any C# file.
- Design new tests beyond the bundle.
- Spawn
bug-investigation(the orchestrator routes failures, not you). - Wait indefinitely. If you cannot run a step: write
status="BLOCKED"withfail_reasonand return. - Mark
status="PASS"while any invariant is unchecked. Either prove it or list it underregressions[].
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 · 68 lines · 47 tokens per session scan A 2eb7a85e1664
verifier is an agent published in the GitHub repository dyCuong03/unity-agent-team (7 stars, last pushed 2mo ago), licensed MIT. It adds 47 tokens to every session and 722 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
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
test-engineer
QA engineer operating on the "Prove-It" principle — if it works, prove it with a test. Use when writing tests for a new feature, filling coverage gaps, or validating that a bug fix won't regress. Can read, write and edit test files. Dispatch with Task tool for isolated test work.
e2e-tester
Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…
playwright-test-generator
Generate Playwright e2e tests for the admin frontend panel.
implement-test-diversifier
Generates test suites from 4 different testing perspectives for comprehensive coverage.