A command that reviews whether completed code changes follow a feature specification. It finds a suitable recent specification, confirms which one to inspect, and sends the review to a specialized verification agent.

Use it after a specification has been implemented when you want to check compliance. You can name the specification directly, or let the command look for recently implemented specifications.

It gives a defined final check after implementation instead of relying only on the person who wrote the code. The review focuses on requirements, scope, affected modules, and the specified tests.

How heiko-braun/draft configures Claude Code

Reuse

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.

Copy the file

curl -O https://raw.githubusercontent.com/heiko-braun/draft/main/.claude/commands/verify.md

Clone the repo

git clone --depth 1 https://github.com/heiko-braun/draft

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/heiko-braun/draft/verify/github.svg)](https://agentmods.dev/commands/heiko-braun/draft/verify)

Your own site

<a href="https://agentmods.dev/commands/heiko-braun/draft/verify"><img src="https://agentmods.dev/badge/commands/heiko-braun/draft/verify/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/heiko-braun/draft/verify"><img src="https://agentmods.dev/badge/commands/heiko-braun/draft/verify.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 19 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 483 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00019	$0.00483
Opus 5.5	$0.00008	$0.00193
Sonnet 5.5	$0.00004	$0.00097
Haiku 4.5	$0.00002	$0.00048

Measured 2mo ago against content hash 44f5ccbb1473, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

verify 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.

.claude/commands/verify.md · 58 lines

What it actually says

Spec Verification Command

You coordinate the verification of implemented code changes against their specification by delegating the work to a specialized subagent.

When to Activate

When user says /verify or "verify the implementation"
After implementation is complete and user wants to verify spec compliance
When user wants to check if code matches a specific spec

Workflow

1. Identify Spec to Review

Check for user input:

If the user provided arguments (e.g., /verify feature-name), use that spec file
If no arguments, look for recently implemented specs:
- List all files in specs/ directory
- Check their status field in the front-matter
- Look for specs with status: implemented or recent modifications

Ask user to confirm:

Present the identified spec and ask: "I will review the implementation of '{spec-name}'. Is this correct?"
If user says no, ask: "Which spec would you like me to review?"

2. Invoke Verification Subagent

Launch the subagent:

When executing this skill, invoke a subagent via the Anthropic API with the following setup:

System prompt: .claude/agents/verify-agent.md
Pass the spec file path as the user message
Parse the subagent's response and use it to complete the task

3. Handle Fixable Issues

After receiving the verification report:

Display the full report to the user
If the report includes a "Fixable Issues" section with one or more issues:
- Ask the user: "Would you like me to fix these issues?"
- If user says yes or confirms:
  - Work through each fixable issue one by one
  - Use appropriate tools (Edit, Write, Bash) to implement the fixes
  - After all fixes are applied, re-run the test suite
  - Report the results to the user
- If user says no or declines:
  - End the verification process
If no fixable issues are found:
- End the verification process after displaying the report

Changes

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 · 58 lines · 19 tokens per session scan A 44f5ccbb1473

Subscribe to this mod's changes

verify is a command published in the GitHub repository heiko-braun/draft (5 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 19 tokens to every session and 483 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.

Code review Testing

audio-pass

Functional audio review for implementation, mix coverage, clarity, and player feedback.

MRCalderon3D/everything-game-dev-code · 15 tokens

test-value-review

Use when a diff adds or changes test files, when a PR claims coverage for config, CI workflows, templates, or HTML output, or when tests look written only to satisfy a "must have tests" rule; not for Playwright selector or performance hygiene (use /playwright-review).

oalders/kitchen-sink · 58 tokens

auditar-refactor

Invoca refactor-safety-auditor — gate canônico antes de qualquer refactor. Coleta evidências (linhas, contrato externo, coverage, mutation) e retorna veredito GO/BLOCK/WARN/GO-OVERRIDE.

luanpdd/kit-mcp · 55 tokens

quality-check-command

This command performs comprehensive code quality checks. Use it before commits or when implementation is complete.

Kazuki-tam/next-stage · 0 tokens

bug-check

Run automated tests and build checks first, then agent code review. For each bug found, propose or document a regression test.

yeaight7/agent-powerups · 25 tokens

claude-loop

Use a fresh headless Claude session (Fable by default) as an independent reviewer of the whole repo, area by area (or of one branch's diff with --base), fix every real finding with regression tests, and loop until each area comes back clean twice in a row. The /codex-loop pattern on Anthropic usage. Runs autonomously.

runnithan/claudex-setup · 72 tokens

draft: Command for Claude Code