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/.cursor/skills/verify/SKILL.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/skills/heiko-braun/draft/verify)<a href="https://agentmods.dev/skills/heiko-braun/draft/verify"><img src="https://agentmods.dev/badge/skills/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.
<a href="https://agentmods.dev/skills/heiko-braun/draft/verify"><img src="https://agentmods.dev/badge/skills/heiko-braun/draft/verify.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.00019 | $0.00490 |
| Opus 5.5 | $0.00008 | $0.00196 |
| Sonnet 5.5 | $0.00004 | $0.00098 |
| Haiku 4.5 | $0.00002 | $0.00049 |
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.
How it starts
The opening of the file, as written. The whole thing — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec Verification Skill
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:
Invoke the verify-agent subagent (located at .cursor/agents/verify-agent.md) to perform the verification:
- Use Cursor's subagent delegation to invoke
/verify-agent - Pass the spec file path as context
- The subagent will analyze code changes, verify compliance, run tests, and generate a detailed report
- Wait for the subagent to complete and return its verification report
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.
- 2mo ago First seen · 58 lines · 19 tokens per session scan A 8b15d7b086a1
verify is a skill 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 490 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 skills, from other repositories
adk-go-self-review
Review an ADK Go change the way a maintainer will — a fresh-context pass over the whole diff, five lenses (correctness and tests, scope, simplicity, style, adk-python parity), and the mutation check that proves your tests pin the change. Use before opening a PR, before any later push that changes code, and when asked…
adversarial-reviewer
Stress-test a code change for concrete correctness defects, unsafe assumptions, and failure modes. Use when the user explicitly asks for an adversarial review, a deep bug hunt, or to tear a change apart, or to check your own change before submitting it. Do not use for ordinary review, style feedback, or general…
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
semgrep-rule-variant-creator
Creates language variants of existing Semgrep rules. Use when porting a Semgrep rule to specified target languages. Takes an existing rule and target languages as input, produces independent rule+test directories for each language.
brooks-sweep
Full-sweep mode: runs a unified analysis across all quality dimensions — code decay, architecture, tech debt, and test quality — then applies fixes directly to the codebase. Safe changes are auto-applied; risky changes are confirmed before execution. Drawing on twelve classic engineering books. Triggers when: user…
plugin-review
Review plugin quality with tiered checks and dependency scoping. Use for PR and pre-release audits.