Borrowing it
Nothing to install: this file belongs to racecraft-lab/racecraft-plugins-public. 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/racecraft-lab/racecraft-plugins-public/main/.specify/extensions/verify-tasks/commands/speckit.verify-tasks.mdgit clone --depth 1 https://github.com/racecraft-lab/racecraft-plugins-publicWrote 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/commands/racecraft-lab/racecraft-plugins-public/speckit.verify-tasks)<a href="https://agentmods.dev/commands/racecraft-lab/racecraft-plugins-public/speckit.verify-tasks"><img src="https://agentmods.dev/badge/commands/racecraft-lab/racecraft-plugins-public/speckit.verify-tasks/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/commands/racecraft-lab/racecraft-plugins-public/speckit.verify-tasks"><img src="https://agentmods.dev/badge/commands/racecraft-lab/racecraft-plugins-public/speckit.verify-tasks.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.00027 | $0.03598 |
| Opus 5 | $0.00014 | $0.01799 |
| Sonnet 5 | $0.00005 | $0.00720 |
| Haiku 4.5 | $0.00003 | $0.00360 |
Grade A, and why
speckit.verify-tasks 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 9d 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.
This is a copy
100% identical to speckit.verify-tasks — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 218 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Input
$ARGUMENTS
You MUST consider the user input before proceeding (if not empty).
Supported arguments: Optional space/comma-separated task IDs to verify only specific tasks. Optional --scope branch|uncommitted|plan-anchored|all (default: all) to control which changes count as evidence.
Display the following advisory immediately before any other work:
⚠️ FRESH SESSION ADVISORY: For maximum reliability, run
/speckit.verify-tasksin a separate agent session from the one that performed/speckit.implement. The implementing agent's context biases it toward confirming its own work.
Pre-Execution Checks
Check for extension hooks (before verification):
-
Check if
.specify/extensions.ymlexists in the project root. -
If it exists, read it and look for entries under the
hooks.before_verify-taskskey -
If the YAML cannot be parsed or is invalid, skip hook checking silently and continue normally
-
Filter to only hooks where
enabled: true -
For each remaining hook, do not attempt to interpret or evaluate hook
conditionexpressions:- If the hook has no
conditionfield, or it is null/empty, treat the hook as executable - If the hook defines a non-empty
condition, skip the hook and leave condition evaluation to the HookExecutor implementation
- If the hook has no
-
For each executable hook, output the following based on its
optionalflag:-
Optional hook (
optional: true):## Extension Hooks **Optional Pre-Hook**: {extension} Command: `/{command}` Description: {description} Prompt: {prompt} To execute: `/{command}` -
Mandatory hook (
optional: false):## Extension Hooks **Automatic Pre-Hook**: {extension} Executing: `/{command}` EXECUTE_COMMAND: {command} Wait for the result of the hook command before proceeding to the Outline.
-
-
If no hooks are registered or
.specify/extensions.ymldoes not exist, skip silently
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.
- 9d ago First seen · 218 lines · 27 tokens per session scan A 81e2dac89d47
speckit.verify-tasks is a command published in the GitHub repository racecraft-lab/racecraft-plugins-public (5 stars, last pushed today), licensed MIT. It adds 27 tokens to every session and 3,598 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to speckit.verify-tasks, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
build
Plan-then-execute against SPEC.md. Native Claude Code loop, no sub-agents.
ui-test
Run VIOS UI tests using the playwright plugin.
validate
Mechanically validate the sonu plugin repo before a PR — manifest sync, YAML frontmatter, shell-fence syntax, named-source and AI-attribution scans, cross-reference integrity, skill reachability. Only meaningful inside the claude-plugins repo; in any other repo, say so and stop.
test-write
Turn a SOLID-verdict ## Test plan critique into real, executing test code via kit:test-writer, one case per matrix row. Never dispatches against a missing, stale, or non-SOLID verdict.
implement-approved-slice
Implement only the approved slice with minimal, explicit, review-friendly changes, then persist execution evidence in slice notes and TASKSTATE.md. The single official execution path of the workflow. Supports an opt-in test-first (TDD) mode, enabled per slice or via --tdd, that writes the failing test before the code…
sdd-implement
Execute a task list in dependency order, tests before implementation for each task, halting on any non-parallel failure instead of pressing ahead.