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 skills/heiko-braun/draft/verifynpx skills add heiko-braun/draft --skill 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.00490 |
| Opus 5 | $0.00010 | $0.00245 |
| Sonnet 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 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.
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.
- 2d 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 1mo ago), licensed Apache-2.0. It adds 19 tokens to every session and 490 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…