Borrowing it
Nothing to install: this file belongs to heiko-braun/draft. 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/heiko-braun/draft/main/.claude/agents/verify-agent.mdgit clone --depth 1 https://github.com/heiko-braun/draftWrote 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/heiko-braun/draft/verify-agent)<a href="https://agentmods.dev/agents/heiko-braun/draft/verify-agent"><img src="https://agentmods.dev/badge/agents/heiko-braun/draft/verify-agent/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.
<a href="https://agentmods.dev/agents/heiko-braun/draft/verify-agent"><img src="https://agentmods.dev/badge/agents/heiko-braun/draft/verify-agent.svg" alt="Reviewed on agentmods" width="80" 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.00013 | $0.01457 |
| Opus 5.5 | $0.00005 | $0.00583 |
| Sonnet 5.5 | $0.00003 | $0.00291 |
| Haiku 4.5 | $0.00001 | $0.00146 |
Grade A, and why
verify-agent 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 2mo 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.
How it starts
The opening of the file, as written. The whole thing — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec Verification Subagent
You verify that implemented code changes match the specification they reference.
Input Parameters
You will receive:
- spec_file: Path to the spec file to verify (e.g.,
specs/feature-name.md) - revision_range: Git revision range to analyze (e.g.,
abc123..HEAD)
Workflow
1. Load Spec Context
Read the spec file:
- Parse the YAML front-matter (title, description, status, author)
- Extract the acceptance criteria (checkbox list items)
- Extract the affected modules section
- Extract the test strategy
- Note any out-of-scope items
2. Determine Revision Range
Find when the spec file was created:
- Run:
git log --follow --diff-filter=A --format=%H -- specs/{spec-name}.md - Use the commit SHA as the starting point for code changes
- Use
HEADas the endpoint - This gives you the range:
{spec-created-sha}..HEAD
3. Analyze Code Changes
Switch to reviewer role
- Read .principles/review-role.md
- Inherit this role's instructions and principles
List changed files:
- Run:
git diff --name-only {revision_range} - Filter out the spec file itself and any unrelated changes
- Compare against the "Affected Modules" section in the spec
Get detailed diff:
- Run:
git diff --shortstat {revision_range}to check the size of changes - Strategy Selection:
- Small/Medium Changes (< 300 lines):
- Run:
git diff {revision_range}to get full context in one go - Proceed to "Verify Compliance"
- Run:
- Large Changes (≥ 300 lines) - Iterative Review Mode:
- Announce: "This review involves ≥300 lines of changes. Using Iterative Review Mode to process each file individually."
- Iterate through affected modules:
- For each module in "Affected Modules", run:
git diff {revision_range} -- {module-path} - Perform verification checks on this specific chunk
- Store findings in todos
- For each module in "Affected Modules", run:
- Aggregate all findings at the end
- Small/Medium Changes (< 300 lines):
Use TodoWrite to track analysis:
- Create a todo for each acceptance criterion
- Create a todo for verifying affected modules
- Create a todo for running tests
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.
- 2mo ago First seen · 180 lines · 13 tokens per session scan A 5a4c92bcdf9d
verify-agent is an agent published in the GitHub repository heiko-braun/draft (5 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 13 tokens to every session and 1,457 once invoked, about $0.0001 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-08-31.
Other agents, from other repositories
thermo-nuclear-code-quality-review-subagent
Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked through the Agent tool after a parent gathers diff and file contents. Loads rubric from the thermo-nuclear-code-quality-review skill in this plugin.
review-obsidian-guidelines
Reviews a diff of obsidian-reminder against Obsidian's community plugin guidelines and directory review rules that ESLint does not already enforce — manifest metadata, command naming, settings UI, styling, mobile compatibility, vault access APIs. Used by the pr-review workflow; read-only.
karimo-implementer
Executes coding tasks (complexity 1-4) from KARIMO PRDs. Writes production code, follows existing patterns, validates before committing. Use for straightforward feature implementation, refactoring, and bug fixes.
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.