racecraft-plugins-public: Skill for Claude Code

.claude/skills/speckit-verify-tasks-run/SKILL.md

speckit-verify-tasks-run is a skill for Claude Code from racecraft-lab/racecraft-plugins-public. It costs 36 tokens per session (3,708 once invoked), scanned A, a copy of speckit-verify-tasks-run, MIT.

A read-only check that tasks marked complete in a task list are backed by real, usable code rather than empty or missing work.

In plain words
What is it for?
Use it to verify selected tasks or all tasks against branch, uncommitted, plan-linked, or repository-wide evidence.
Why use it?
It helps catch tasks that were marked done even though their expected code is absent or inactive.

Skill for Claude Code

Written for Claude Code: disable-model-invocation in frontmatter.

This is racecraft-lab/racecraft-plugins-public's own configuration. It tells Claude Code how to work on racecraft-plugins-public itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything racecraft-plugins-public configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/racecraft-lab/racecraft-plugins-public/main/.claude/skills/speckit-verify-tasks-run/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/racecraft-lab/racecraft-plugins-public

Made for: Claude Code.

Wrote 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.

agentmods badge for speckit-verify-tasks-run

README.md
[![agentmods](https://agentmods.dev/badge/skills/racecraft-lab/racecraft-plugins-public/speckit-verify-tasks-run/github.svg)](https://agentmods.dev/skills/racecraft-lab/racecraft-plugins-public/speckit-verify-tasks-run)
Your own site
<a href="https://agentmods.dev/skills/racecraft-lab/racecraft-plugins-public/speckit-verify-tasks-run"><img src="https://agentmods.dev/badge/skills/racecraft-lab/racecraft-plugins-public/speckit-verify-tasks-run/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.

agentmods 80×15 button for speckit-verify-tasks-run

Your own site · 80×15
<a href="https://agentmods.dev/skills/racecraft-lab/racecraft-plugins-public/speckit-verify-tasks-run"><img src="https://agentmods.dev/badge/skills/racecraft-lab/racecraft-plugins-public/speckit-verify-tasks-run.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 36 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,708 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 94% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00036 $0.03708
Opus 5 $0.00018 $0.01854
Sonnet 5 $0.00007 $0.00742
Haiku 4.5 $0.00004 $0.00371

Measured 11d ago against content hash 11a2852c0dd7, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

speckit-verify-tasks-run 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 11d 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.

Origin

This is a copy

94% identical to speckit-verify-tasks-run — 9 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.

.claude/skills/speckit-verify-tasks-run/SKILL.md · 225 lines

How it starts

The opening of the file, as written. The whole thing — 225 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Verify Tasks Run Skill

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-tasks in 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.yml exists in the project root.
  • If it exists, read it and look for entries under the hooks.before_verify-tasks key
  • 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 condition expressions:
    • If the hook has no condition field, 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
  • When constructing command invocations from hook command names, replace dots (.) with hyphens (-). For example, speckit.git.commit/speckit-git-commit.
  • For each executable hook, output the following based on its optional flag:
    • 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.
      

Read the full file on GitHub · 225 lines

Changes

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.

  1. 11d ago First seen · 225 lines · 36 tokens per session scan A 11a2852c0dd7

Subscribe to this mod's changes

speckit-verify-tasks-run is a skill published in the GitHub repository racecraft-lab/racecraft-plugins-public (5 stars, last pushed today), licensed MIT. It adds 36 tokens to every session and 3,708 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to speckit-verify-tasks-run, differing in 9 lines, and is treated as a copy.

Related

Other skills, from other repositories

bug-investigator

Use when encountering any bug, test failure, or unexpected behavior during spec-superflow execution, before proposing fixes. Invoked automatically when build-executor hits a blockage.

MageByte-Zero/spec-superflow · 37 tokens

backprop

Bug → spec protocol. When a bug is found or a test fails, trace the cause, decide whether a new §V invariant would catch recurrence, append to §B. This is the one non-obvious thing SDD does that plan-then-execute doesn't. Triggers on test failure, bug report, post-mortem, or explicit user ask.

JuliusBrussee/cavekit · 76 tokens

check

Read-only drift detector. Diffs SPEC.md against current code and reports violations grouped by severity. Writes nothing — suggests remedies via the spec or build skills but never invokes them. Triggers when the user asks to check drift, audit the spec, verify invariants, or ask whether code still matches the spec.…

JuliusBrussee/cavekit · 102 tokens

speq-audit

Audit a speq project's health — spec-library structure, feature/decision-log/plan validation, mission-to-spec sync, unrecorded plans, and gitignore hygiene — then guide fixes. Use when the user asks to audit, health-check, doctor, lint, or sanity-check the specs or repo, or after cloning or inheriting a speq project.

marconae/speq-skill · 77 tokens

error-design

Reviews error handling and exception design, applying the "define errors out of existence" principle. Use when reviewing error handling, when a module throws too many exceptions, or when callers must handle errors they shouldn't need to know about. Not for general caller-burden complexity (use pull-complexity-down)…

codybrom/clairvoyance · 75 tokens

diagnose

Routes a vague symptom or complaint to the most relevant Clairvoyance skill via a decision tree. Use when someone describes a problem but doesn't know which skill to reach for. Not for a comprehensive review (use design-review) or a checklist scan (use red-flags).

codybrom/clairvoyance · 57 tokens