racecraft-plugins-public: Skill for Claude Code

.agents/skills/speckit-specify/SKILL.md

speckit-specify is a skill for Claude Code, Codex from racecraft-lab/racecraft-plugins-public. It costs 19 tokens per session (4,037 once invoked), scanned A, a copy of speckit-specify, MIT.

A skill for turning a plain-language feature request into a written feature specification, or updating an existing one.

In plain words
What is it for?
Use it when starting or revising a feature specification from a user's requirements.
Why use it?
It gives coding work a clear description of what should be built and can account for project-specific steps that must happen before specification.

Skill for Claude CodeCodex

Written for Claude Code: $ARGUMENTS substitution. Also seen: installed under .agents/ (shared by several agents); $skill-name invocation.

This is racecraft-lab/racecraft-plugins-public's own configuration. It tells Claude Code and Codex 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/.agents/skills/speckit-specify/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/racecraft-lab/racecraft-plugins-public

Made for: Claude Code, Codex.

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-specify

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/racecraft-lab/racecraft-plugins-public/speckit-specify"><img src="https://agentmods.dev/badge/skills/racecraft-lab/racecraft-plugins-public/speckit-specify.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 19 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,037 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 89% 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.00019 $0.04037
Opus 5 $0.00010 $0.02018
Sonnet 5 $0.00004 $0.00807
Haiku 4.5 $0.00002 $0.00404

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

Security

Grade A, and why

speckit-specify 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

89% identical to speckit-specify — 135 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.

.agents/skills/speckit-specify/SKILL.md · 346 lines

How it starts

The opening of the file, as written. The whole thing — 346 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).

Pre-Execution Checks

Check for extension hooks (before specification):

  • Check if .specify/extensions.yml exists in the project root.
  • If it exists, read it and look for entries under the hooks.before_specify key
  • If the YAML cannot be parsed or is invalid, skip hook checking silently and continue normally
  • Filter out hooks where enabled is explicitly false. Treat hooks without an enabled field as enabled by default.
  • 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.
      
      After emitting the block above you MUST actually invoke the hook and wait for it to finish before continuing. Run it the same way you would run the command yourself in this agent/session (the invocation may differ from the literal {command} id shown above, e.g. a skills-mode agent runs it as /skill:speckit-... or $speckit-...). Emitting the block alone does not run the hook.
  • If no hooks are registered or .specify/extensions.yml does not exist, skip silently

Read the full file on GitHub · 346 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 · 346 lines · 19 tokens per session scan A 88d7fab201de

Subscribe to this mod's changes

speckit-specify is a skill published in the GitHub repository racecraft-lab/racecraft-plugins-public (5 stars, last pushed today), licensed MIT. It adds 19 tokens to every session and 4,037 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to speckit-specify, differing in 135 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