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 commands/heiko-braun/draft/verifygit clone --depth 1 https://github.com/heiko-braun/draftWhat 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.00019 | $0.00483 |
| Opus 5 | $0.00010 | $0.00242 |
| Sonnet 5 | $0.00004 | $0.00097 |
| Haiku 4.5 | $0.00002 | $0.00048 |
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 2d 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
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
/verifyor "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
statusfield in the front-matter - Look for specs with
status: implementedor recent modifications
- List all files in
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
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.
- 2d ago First seen · 58 lines · 19 tokens per session scan A 44f5ccbb1473
verify is a command published in the GitHub repository heiko-braun/draft (5 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 19 tokens to every session and 483 once invoked, about $0.0001 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.