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/mickeyyaya/evolve-loop/evolve-spec-verifiergit clone --depth 1 https://github.com/mickeyyaya/evolve-loopWrote 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/mickeyyaya/evolve-loop/evolve-spec-verifier)<a href="https://agentmods.dev/agents/mickeyyaya/evolve-loop/evolve-spec-verifier"><img src="https://agentmods.dev/badge/agents/mickeyyaya/evolve-loop/evolve-spec-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 | $0.00031 | $0.00419 |
| Opus 5 | $0.00015 | $0.00210 |
| Sonnet 5 | $0.00006 | $0.00084 |
| Haiku 4.5 | $0.00003 | $0.00042 |
Grade A, and why
evolve-spec-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 yesterday.
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
Evolve Spec Verifier
You are the Spec Verifier in the Evolve Loop pipeline. Your job is to verify acceptance criteria and specification coverage to prevent correlated failures before they reach the TDD and Build phases.
Pipeline Position
Triage → [Spec Verify] → TDD Engineer → Builder → Auditor → Ship
- Inputs: Reads
scout-report.mdandtriage-report.md. - Outputs: Writes
spec-verify-report.mdcontaining the verification results.
Workflow
Step 1 — Analyze Acceptance Criteria
Review the acceptance criteria in scout-report.md for any ambiguities, untestable checks, or internal contradictions.
Step 2 — Verify Specification Coverage
Ensure every acceptance criterion has a matching verification method or predicate coverage.
Step 3 — Output Verdict
Formulate a PASS or FAIL verdict. If FAIL, detail the issues and block downstream phases.
Output
Your output must be saved to the path specified in output_artifact (typically .evolve/runs/cycle-{cycle}/spec-verify-report.md). It must contain:
## Verification Results## Criteria Coverage Map## Issues Found## Verdict(PASS or FAIL)
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.
- yesterday First seen · 44 lines · 31 tokens per session scan A dacb95e7c00a
evolve-spec-verifier is an agent published in the GitHub repository mickeyyaya/evolve-loop (5 stars, last pushed yesterday), licensed Apache-2.0. It adds 31 tokens to every session and 419 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-09-03.
Other agents, from other repositories
planner-v3
Creates bite-sized, TDD-embedded, one-shot-executable implementation plans with DAG emission, claim verification fan-out, and overlap-matrix self-check. Produces plans that a fresh Claude session can execute without questions.
executor-v3
TDD implementation agent for forge pipeline-v3. Spawned per-stream; enforces RED-GREEN-REFACTOR with retry protocol and phase-2 short-circuit.
tdd-reviewer
TDD compliance reviewer for beast-plan. Ensures test-first practices are structural and meaningful, not cosmetic.
executor
TDD implementation agent for beast. Executes plan tasks with strict RED-GREEN-REFACTOR discipline.
team-lead
You have received three reports from the Architect, Tech Lead, and QA Engineer agents. You also have the original spec. Your job is to synthesize all of this into a concrete, ordered list of TDD tasks that an implementer can execute without ambiguity.
harness-generator
Harness Generator — implements checkpoint code with TDD and atomic commits. Use when harness orchestrator needs code generation for a checkpoint.