speckit.clarify

speckit.clarify is a command for Claude Code from HelixDevelopment/code. It costs 27 tokens per session (4,112 once invoked), scanned A, a copy of clarify, MIT.

A specification-review command that finds unclear or underspecified parts of a feature description by asking targeted questions. It records the answers back in the specification.

In plain words
What is it for?
Use it to clarify missing decisions and update a feature specification with the user's answers.
Why use it?
It resolves important unknowns before planning or coding, reducing the chance of building on ambiguous requirements.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

Good fit Use it to clarify missing decisions and update a feature specification with the user's answers.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/helixdevelopment/code/speckit.clarify
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo
git clone --depth 1 https://github.com/HelixDevelopment/code

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/commands/helixdevelopment/code/speckit.clarify/github.svg)](https://agentmods.dev/commands/helixdevelopment/code/speckit.clarify)
Your own site
<a href="https://agentmods.dev/commands/helixdevelopment/code/speckit.clarify"><img src="https://agentmods.dev/badge/commands/helixdevelopment/code/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/commands/helixdevelopment/code/speckit.clarify"><img src="https://agentmods.dev/badge/commands/helixdevelopment/code/speckit.clarify.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 27 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 4,112 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.00027 $0.04112
Opus 5 $0.00014 $0.02056
Sonnet 5 $0.00005 $0.00822
Haiku 4.5 $0.00003 $0.00411

Measured yesterday against content hash 0656a0171e55, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-15, 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 yesterday.

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 clarify — 18 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.

.kilo/commands/speckit.clarify.md · 288 lines

How it starts

The opening of the file, as written. The whole thing — 288 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
  • 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 · 288 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. yesterday Changed 0656a0171e55
  2. 4d ago First seen · 288 lines · 27 tokens per session scan A ae3efd8a50a6

Subscribe to this mod's changes

speckit.clarify is a command published in the GitHub repository HelixDevelopment/code (2 stars, last pushed 2d ago), licensed MIT. It adds 27 tokens to every session and 4,112 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to clarify, differing in 18 lines, and is treated as a copy.