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/flurdy/agent-skills/verify-tasknpx skills add flurdy/agent-skills --skill verify-taskgit clone --depth 1 https://github.com/flurdy/agent-skillsWrote 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/flurdy/agent-skills/verify-task)<a href="https://agentmods.dev/skills/flurdy/agent-skills/verify-task"><img src="https://agentmods.dev/badge/skills/flurdy/agent-skills/verify-task.svg" alt="Measured on agentmods" 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 | $0.00033 | $0.01780 |
| Opus 5 | $0.00016 | $0.00890 |
| Sonnet 5 | $0.00007 | $0.00356 |
| Haiku 4.5 | $0.00003 | $0.00178 |
Grade A, and why
verify-task 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 3d 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 — 224 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verify Task
Check that an implementation fulfills its task requirements and that tests adequately cover the changes.
When to Use
- After finishing implementation, before committing
- When unsure if test coverage is sufficient
- As a quality gate before
/complete-task - When reviewing your own work for completeness
Usage
/verify-task # Auto-detect in-progress bead
/verify-task <bead-id> # Verify against a specific bead
Instructions
Tier guard
This skill is model-tier: premium. Before starting, check which model you are
running as. If it is below the premium tier for this runtime (e.g. Sonnet or Haiku in
Claude Code), say so and ask via AskUserQuestion whether to:
- Continue here — accept reduced depth on this run
- Stop — switch model (
/modelin Claude Code) or rerun in a premium session
Skip the prompt when the user explicitly chose the current model. On a premium model, stay silent and proceed.
1. Identify the Task
# If bead ID provided, use it directly
bd show <bead-id>
# Otherwise, find the in-progress bead
bd list --status=in_progress
If multiple beads are in progress, ask the user which one to verify.
2. Gather Context
Collect the full picture of what changed and what was required:
# Read the bead requirements
bd show <bead-id>
# See what files changed
git status
git diff
git diff --cached
Read the bead description carefully. Extract:
- Explicit requirements — what the bead says to do
- Implicit requirements — obvious behaviors that follow from the description (e.g., a "delete" feature implies confirmation, error handling)
- Type of change — feature, bug fix, refactor, config, docs, chore
3. Verify Requirements Are Met
Read each changed file. Compare the implementation against the requirements.
Check:
- Every explicit requirement from the bead is addressed
- The implementation is functionally correct (logic, data flow)
- No partial implementations left behind (TODOs, placeholder code)
- Changes are scoped to the task (no unrelated modifications)
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.
- 3d ago First seen · 224 lines · 33 tokens per session scan A 723c5320660c
verify-task is a skill published in the GitHub repository flurdy/agent-skills (7 stars, last pushed 5d ago), licensed MIT. It adds 33 tokens to every session and 1,780 once invoked, about $0.0002 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…