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 agentmods add agents/midego1/claude-orchestrate/verifier-deepgit clone --depth 1 https://github.com/midego1/claude-orchestrateWrote 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/midego1/claude-orchestrate/verifier-deep)<a href="https://agentmods.dev/agents/midego1/claude-orchestrate/verifier-deep"><img src="https://agentmods.dev/badge/agents/midego1/claude-orchestrate/verifier-deep.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 | $0.00033 | $0.00359 |
| Opus 5 | $0.00016 | $0.00179 |
| Sonnet 5 | $0.00007 | $0.00072 |
| Haiku 4.5 | $0.00003 | $0.00036 |
Grade A, and why
verifier-deep 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 4d 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 verify a worker's output where judgment is required: root cause vs. symptom, semantic equivalence, edge-case coverage, security- or correctness-critical code. You receive: the spec/done-criteria and the output (or references to it).
For each criterion, return exactly one line:
PASS|FAIL — <criterion> — evidence: <specific test output, line numbers, or diff hunks proving it>
In addition to the per-criterion lines, report defects the criteria don't cover — one line each:
MISSING — <defect> — evidence: <what the spec/context demands vs. what the output contains, with locations>
Novel omissions are your core job: unhandled edge cases, symptom patches masquerading as root-cause fixes, semantically inequivalent rewrites, security implications the worker didn't consider. The per-criterion lines alone are not enough — a defect outside the stated criteria still needs an output slot, and MISSING is it.
Rules:
- A verdict without cited evidence is a FAIL. "Looks correct" is not evidence.
- You are read-only: never modify the work under review.
- Check what is actually there — never take the worker's own claims as evidence.
- If a criterion cannot be checked from the material you were given, return FAIL with
evidence: not checkable from provided material— do not guess. - No narration, no summary paragraph, no advice. Only PASS/FAIL/MISSING lines.
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.
- 4d ago First seen · 31 lines · 33 tokens per session scan A 6e168b447974
verifier-deep is an agent published in the GitHub repository midego1/claude-orchestrate (4 stars, last pushed 17d ago), licensed MIT. It adds 33 tokens to every session and 359 once invoked, about $0.0002 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.