verifier

verifier is an agent for Claude Code from dyCuong03/unity-agent-team. It costs 47 tokens per session (722 once invoked), scanned A, original, MIT.

A verification agent that runs the checks described in an implementation result and writes a structured verification result. It is intended for small and medium tasks and does not design tests or edit code.

In plain words
What is it for?
Use it to run an existing verification bundle and report whether the implementation passed its required checks.
Why use it?
It separates checking completed work from implementing it, while following a defined verification procedure and project scope.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter; reads .claude/ paths.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is python .claude/scripts/orchestrate.py validate workspace/verification_result.json verification_result.

Good fit Use it to run an existing verification bundle and report whether the implementation passed its required checks.

Compare 6 agents from other repositories ↓
Install

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.

Clone the repo
git clone --depth 1 https://github.com/dyCuong03/unity-agent-team
agentmods
npx agentmods add agents/dycuong03/unity-agent-team/verifier

Made for: Claude Code.

Wrote 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.

agentmods badge for verifier

README.md
[![agentmods](https://agentmods.dev/badge/agents/dycuong03/unity-agent-team/verifier/github.svg)](https://agentmods.dev/agents/dycuong03/unity-agent-team/verifier)
Your own site
<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.

agentmods 80×15 button for verifier

Your own site · 80×15
<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>
Per session 47 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 722 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 11d ago against content hash 2eb7a85e1664, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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.

.claude/agents/verifier.md · 68 lines

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

  1. Read (Read tool, skip if already in context) .claude/skills/verifier/SKILL.md for the 5-step procedure.

  2. 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).

  3. Read workspace/impl_result.json. If it is missing, malformed, has compilation != "CLEAN", or has an empty verification_bundle.invariants: set status="BLOCKED" and stop.

  4. Run every repro_step. Use MCP (ai-game-developer) for scene/log inspection. Use tests-run if the bundle references tests by name.

  5. Check every invariant. Each violation is a regression entry.

  6. Sample at least 50% of edge_cases[]. Note skipped ones under notes.

  7. Emit workspace/verification_result.json via direct Write tool. Then validate it:

    python .claude/scripts/orchestrate.py validate workspace/verification_result.json verification_result
    
  8. 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" with fail_reason and return.
  • Mark status="PASS" while any invariant is unchecked. Either prove it or list it under regressions[].

Read the full file on GitHub · 68 lines

Changes

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.

  1. 11d ago First seen · 68 lines · 47 tokens per session scan A 2eb7a85e1664

Subscribe to this mod's changes

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.

Related

Other agents, from other repositories