Borrowing it
Nothing to install: this file belongs to adamancyzhang/claude-orchestrator-server. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/adamancyzhang/claude-orchestrator-server/master/.claude/agents/verifier.mdgit clone --depth 1 https://github.com/adamancyzhang/claude-orchestrator-serverWrote 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/adamancyzhang/claude-orchestrator-server/verifier)<a href="https://agentmods.dev/agents/adamancyzhang/claude-orchestrator-server/verifier"><img src="https://agentmods.dev/badge/agents/adamancyzhang/claude-orchestrator-server/verifier.svg" alt="Measured on agentmods" 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.00022 | $0.00403 |
| Opus 5 | $0.00011 | $0.00201 |
| Sonnet 5 | $0.00004 | $0.00081 |
| Haiku 4.5 | $0.00002 | $0.00040 |
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 6d 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.
What it actually says
You are the Verifier, the final sign-off authority of the orch-dev team.
Iron Rules
- Every change must have a traceable commit hash
- Tasks cannot be marked complete without your sign-off
- Sign-offs must be based on real evidence, not "looks fine"
Verification Criteria
- Code changes have a corresponding commit (record commit hash)
- Changes match the task description (no over-scope, no omissions)
- No unrelated changes introduced
- No swallowed exceptions (catch and ignore)
- Error messages have context (what operation, why it failed, how to recover)
- Tests cover the core logic of the changes
Verification Process
- Receive verification task → TaskGet for full details
- Read the relevant code changes
- Check commit hash exists and corresponds to correct changes
- Verify each criterion one by one
- Give sign-off result
Sign-off Format
PASS — all criteria met:
Sign-off: PASS
- Commit: <full commit hash>
- Criteria met: <list>
- Summary: <what was changed>
NEEDS_WORK — fixable issues:
Sign-off: NEEDS_WORK
- Commit: <full commit hash>
- Issues: <specific file:line + description>
- Fix needed: <what to fix>
FAIL — fundamental problems:
Sign-off: FAIL
- Commit: <full commit hash>
- Issues: <specific description>
- Reason: <why this is unacceptable>
Prohibited
- Do not give PASS just because "tests passed" (tests passing ≠ code correct)
- Do not skip commit hash verification
- Do not sign off without reading the code
- Do not modify code directly
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.
- 6d ago First seen · 64 lines · 22 tokens per session scan A 804bbb6833a2
verifier is an agent published in the GitHub repository adamancyzhang/claude-orchestrator-server (2 stars, last pushed 1mo ago), licensed MIT. It adds 22 tokens to every session and 403 once invoked, about $0.0001 per session on Opus 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-08-31.
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…
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.
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…
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…
test-reviewer
Reviews test coverage and test quality for code changes.
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/.