racecraft-plugins-public: Skill for Claude Code

.claude/skills/speckit-validate/SKILL.md

speckit-validate is a skill for Claude Code from racecraft-lab/racecraft-plugins-public. It costs 20 tokens per session (716 once invoked), scanned A, a copy of speckit-speckit-utils-validate, MIT.

A checker that compares a feature’s written specification with its task list and completed files. It verifies task status, expected file paths, and links between requirements and work.

In plain words
What is it for?
Validating completed specification-driven work, finding missing files, and reporting requirements or tasks that lack traceable implementation evidence.
Why use it?
A checked task does not always mean the expected file exists or that the implementation matches the specification. This exposes those gaps.

Skill for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

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-validate/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-validate

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/racecraft-lab/racecraft-plugins-public/speckit-validate"><img src="https://agentmods.dev/badge/skills/racecraft-lab/racecraft-plugins-public/speckit-validate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 20 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 716 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 88% 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.00020 $0.00716
Opus 5 $0.00010 $0.00358
Sonnet 5 $0.00004 $0.00143
Haiku 4.5 $0.00002 $0.00072

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

Security

Grade A, and why

speckit-validate 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.

Origin

This is a copy

88% identical to speckit-speckit-utils-validate — 12 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-validate/SKILL.md · 85 lines

How it starts

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

User Input

$ARGUMENTS

Outline

Deterministically verify that the implementation matches the specification by checking task completion, file existence, and requirement traceability.

Step 1: Select feature

If $ARGUMENTS specifies a feature name or number, use that. Otherwise, find the most recently modified feature in specs/.

If no features exist, error: "No features found in specs/. Run /speckit.specify first."

Step 2: Parse tasks

Read tasks.md from the feature directory. Parse each checkbox line:

  • Extract task text (after - [x] or - [ ])
  • Mark as completed or remaining
  • Extract keywords: file paths (auth/login.py), snake_case names (user_auth), CamelCase names (UserAuth), dotted names (config.yaml)

If no tasks.md exists, error: "No tasks.md found. Run /speckit.tasks first."

Step 3: Verify completed task artifacts

For each completed task that references file paths:

  1. Search the project directory for the referenced file
  2. If found: PASS
  3. If not found: WARN ("task says 'Create auth/login.py' but file not found")

Skip verification for:

  • Incomplete tasks (not yet implemented)
  • Tasks with no file path references (e.g., "Set up CI pipeline")

Step 4: Parse spec requirements

Read spec.md from the feature directory. Extract items from the "Functional Requirements" section (bulleted list items under that heading).

If no requirements section found, skip to Step 6.

Step 5: Trace requirements to tasks

For each requirement, search task descriptions for matching keywords:

  • Tokenize the requirement into significant words (skip stop words)
  • Check each task's text for overlap (2+ matching keywords = traced)

Report:

  • Requirement with matching tasks: PASS ("traced to Task N")
  • Requirement with no matching tasks: WARN ("no task found for this requirement")

Step 6: Report

Output a validation report:

Validation Report: 001-auth
============================

Task Completion: 3/5 (60%)
  [x] Task 1: Create auth/login.py      -> auth/login.py FOUND
  [x] Task 2: Add password hashing      -> (no file reference)
  [x] Task 3: Write auth tests          -> tests/test_auth.py FOUND
  [ ] Task 4: Add rate limiting         -> (not yet implemented)
  [ ] Task 5: Update API docs           -> (not yet implemented)

Requirement Traceability: 3/3
  "Users can log in with email"          -> Task 1 (PASS)
  "Passwords are stored securely"        -> Task 2 (PASS)
  "Users can reset password via email"   -> (no matching task - WARN)

Summary: 2 PASS, 1 WARN, 0 FAIL

Read the full file on GitHub · 85 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. 9d ago First seen · 85 lines · 20 tokens per session scan A 55bd292b3148

Subscribe to this mod's changes

speckit-validate is a skill published in the GitHub repository racecraft-lab/racecraft-plugins-public (5 stars, last pushed today), licensed MIT. It adds 20 tokens to every session and 716 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to speckit-speckit-utils-validate, differing in 12 lines, and is treated as a copy.

Related

Other skills, from other repositories

build-executor

Govern implementation from an approved execution contract. Invoke when execution-contract.md is approved and the user wants disciplined build work, TDD execution, or guarded batch-by-batch implementation.

MageByte-Zero/spec-superflow · 39 tokens

workflow-start

Primary entry point for the spec-superflow state-machine workflow. Invoke when the user is inside an active spec-superflow change directory (look for .spec-superflow.yaml, changes/ /, proposal.md, specs/, design.md, tasks.md, or execution-contract.md) and asks to start, continue, resume, implement, plan, or figure out…

MageByte-Zero/spec-superflow · 125 tokens

release-archivist

Close out a spec-superflow change with verification, summary, and archive readiness. Invoke when implementation is complete, verification is underway, or the user asks for a final wrap-up.

MageByte-Zero/spec-superflow · 42 tokens

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

spec-writer

Create or refine spec-superflow planning artifacts. Invoke when the change is understood well enough to write proposal.md, specs/, design.md, and tasks.md.

MageByte-Zero/spec-superflow · 35 tokens

contract-builder

Convert approved planning artifacts into an execution contract. Invoke when the user wants to start building, asks to move from planning to implementation, or when execution-contract.md is missing or stale.

MageByte-Zero/spec-superflow · 39 tokens