racecraft-plugins-public: Skill for Claude Code

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

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

A feature-specification review workflow that asks up to five focused questions about unclear requirements. It records the answers back in the current Spec Kit feature specification.

In plain words
What is it for?
Use it when a feature request is incomplete or ambiguous, especially before planning or coding begins.
Why use it?
It exposes missing decisions before implementation, reducing the chance that an agent or developer builds the wrong behavior.

Skill for Claude Code

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

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/racecraft-lab/racecraft-plugins-public/speckit-clarify"><img src="https://agentmods.dev/badge/skills/racecraft-lab/racecraft-plugins-public/speckit-clarify.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 34 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,233 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 98% 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.00034 $0.04233
Opus 5.5 $0.00014 $0.01693
Sonnet 5.5 $0.00007 $0.00847
Haiku 4.5 $0.00003 $0.00423

Measured 21d ago against content hash f6acfbc82c96, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

speckit-clarify 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 21d 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

98% identical to speckit-clarify — 22 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-clarify/SKILL.md · 292 lines

How it starts

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

  • Check if .specify/extensions.yml exists in the project root.
  • If it exists, read it and look for entries under the hooks.before_clarify key
  • If the YAML cannot be parsed or is invalid, do not skip silently: tell the user that .specify/extensions.yml could not be read (include the parser error) and that no hooks were checked, including any mandatory (optional: false) hooks registered there, then 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 · 292 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. 21d ago Changed f6acfbc82c96
  2. 1mo ago First seen · 292 lines · 34 tokens per session scan A d3aa120d6b5d

Subscribe to this mod's changes

speckit-clarify is a skill published in the GitHub repository racecraft-lab/racecraft-plugins-public (5 stars, last pushed 6d ago), licensed MIT. It adds 34 tokens to every session and 4,233 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 98% identical to speckit-clarify, differing in 22 lines, and is treated as a copy.

Related

Other skills, from other repositories

build-executor

Execute an active direct request or approved planned change. Native continuous implementation is the default; existing legacy changes retain their recorded contract obligations.

MageByte-Zero/spec-superflow · 30 tokens

contract-builder

Maintain an execution contract only for an existing legacy change that requires one. New direct/planned changes do not invoke this skill when a contract is absent.

MageByte-Zero/spec-superflow · 33 tokens

codex-issue-coordinator

Coordinates a large batch of GitHub issues through separate Codex worker threads, tested pull requests, review loops, and gated merges. Use when the user asks one Codex thread to manage several coding sessions or complete a parent issue, milestone, or issue batch.

owainlewis/blueprint · 59 tokens

plan

Turns a reviewed spec or decided brief into ordered tasks for separate agent runs. Use for implementation tasks, tracker tickets, or useful milestones. Do not use for one coding task or its short execution outline.

owainlewis/blueprint · 42 tokens

review

Uses a fresh agent to review an implementation change without editing it. Checks behavior, security, regressions, complexity, tests, docs, and missing proof. Use for code, PR, diff, security, second-opinion, or pre-merge reviews.

owainlewis/blueprint · 53 tokens

html-doc

Generates a polished, static HTML reading view from an existing Markdown PRD or technical design. Use when a user asks to render, present, visualize, or make a PRD or design document easier for humans to read in a browser.

owainlewis/blueprint · 51 tokens