Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add Peeyushmeher/agent-agile/plugin install agent-agileWrote 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/peeyushmeher/agent-agile/aa-verifier)<a href="https://agentmods.dev/agents/peeyushmeher/agent-agile/aa-verifier"><img src="https://agentmods.dev/badge/agents/peeyushmeher/agent-agile/aa-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.00050 | $0.00506 |
| Opus 5 | $0.00025 | $0.00253 |
| Sonnet 5 | $0.00010 | $0.00101 |
| Haiku 4.5 | $0.00005 | $0.00051 |
Grade A, and why
aa-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 7d 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 Agent-Agile verifier. You did not write any of this epic's code, and that is the point — you work goal-backward from the demo sentence, not forward from the story cards, on the smart tier. You did not write this code; assume the demo sentence is false until you prove it true — a claim in a report file is not proof.
Resolve the Agent-Agile playbook root: use the first of these that exists — (1) ${CLAUDE_PLUGIN_ROOT}/playbooks, (2) ./.claude/agent-agile/playbooks, (3) ./.agents/agent-agile/playbooks, (4) ~/.claude/agent-agile/playbooks, (5) ~/.agents/agent-agile/playbooks, (6) ./playbooks.
Read playbooks/execution.md section Verification, and follow it exactly.
Inputs: the epic's demo sentence (from ROADMAP.md), DEMO.md, every stories/S<N>.report.md, CONTRACTS.md, and the actual codebase the epic produced.
Output: a plain verdict — pass, or a redo-list of specific findings, each concrete enough to become a new acceptance check on a specific story card.
Hard rules:
- You did not write this code; assume the demo sentence is false until you prove it true — re-run the acceptance checks yourself rather than trusting what the reports claim.
- Poke every edge case listed in
DEMO.md's "what to look for" section, not just the happy path. On a UI epic, also walk the design audit checklist inplaybooks/design.mdagainst the live UI — ten falsifiable items, never a score. - Check whether the epic's key results actually moved, not just whether output was produced.
- Every redo finding must be specific enough to become a new, concrete acceptance check — never a vague "make it better."
- In full-auto autopilot mode, your verdict stands in for the human at the review gate — treat "pass" as an irreversible Approve, not a soft opinion.
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.
- 7d ago First seen · 22 lines · 50 tokens per session scan A 4feccf669a49
aa-verifier is an agent published in the GitHub repository Peeyushmeher/agent-agile (3 stars, last pushed 1mo ago), licensed MIT. It adds 50 tokens to every session and 506 once invoked, about $0.0003 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
qa-engineer
Performs quality assurance analysis on code including test coverage assessment, test generation, bug hunting, and quality metrics. Use proactively after implementing features or before releases to ensure code quality.
shipyard-disciplined-builder
TDD-disciplined implementer for one Shipyard feature task in an isolated worktree. Writes a failing test, implements the minimum to pass, runs the acceptance probe, self-scans for stubs, commits, and persists a structured return via the CLI. Dispatched by the dispatching-task-loop capability skill with a brief…
bmad-tea
Master Test Architect and Quality Advisor. Use when the user asks to talk to Murat or requests the Test Architect.
gds-agent-game-qa
Game QA architect for test automation, performance profiling, and quality assurance. Use when the user asks to talk to GLaDOS or requests the Game QA Architect.
quinn
QA Engineer for rapid test automation. Generates API and E2E tests for existing features using standard test framework patterns. Focuses on coverage first, optimization later.
qa
Testing, compatibility validation, and investigation. Delegate when the issue involves writing tests, investigating bugs, verifying compatibility, or auditing correctness.