speckit-clarify

speckit-clarify is a skill for Claude Code from dfirs1car1o/sicario-spec. It costs 34 tokens per session (3,698 once invoked), scanned A, a copy of speckit-clarify, MIT.

A specification review process that finds unclear or missing requirements by asking up to five focused questions and adding the answers to the feature specification.

In plain words
What is it for?
Use it to review an incomplete feature brief, check project clarification hooks, ask targeted questions, and record the resulting decisions in the specification.
Why use it?
It helps resolve ambiguity before implementation, so developers are less likely to build the wrong behavior or overlook important requirements.

Skill for Claude Code

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

Good fit Use it to review an incomplete feature brief, check project clarification hooks, ask targeted questions, and record the resulting decisions in the specification.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/dfirs1car1o/sicario-spec/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.

Any agent
npx skills add dfirs1car1o/sicario-spec --skill speckit-clarify
Clone the repo
git clone --depth 1 https://github.com/dfirs1car1o/sicario-spec

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/dfirs1car1o/sicario-spec/speckit-clarify/github.svg)](https://agentmods.dev/skills/dfirs1car1o/sicario-spec/speckit-clarify)
Your own site
<a href="https://agentmods.dev/skills/dfirs1car1o/sicario-spec/speckit-clarify"><img src="https://agentmods.dev/badge/skills/dfirs1car1o/sicario-spec/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/dfirs1car1o/sicario-spec/speckit-clarify"><img src="https://agentmods.dev/badge/skills/dfirs1car1o/sicario-spec/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 3,698 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.00034 $0.03698
Opus 5 $0.00017 $0.01849
Sonnet 5 $0.00007 $0.00740
Haiku 4.5 $0.00003 $0.00370

Measured 12d ago against content hash 08e643cb56c8, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, 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 12d 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-clarify — 14 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 · 284 lines

How it starts

The opening of the file, as written. The whole thing — 284 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, 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 slash commands 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.
      
  • If no hooks are registered or .specify/extensions.yml does not exist, skip silently

Outline

Goal: Detect and reduce ambiguity or missing decision points in the active feature specification and record the clarifications directly in the spec file.

Note: This clarification workflow is expected to run (and be completed) BEFORE invoking /speckit-plan. If the user explicitly states they are skipping clarification (e.g., exploratory spike), you may proceed, but must warn that downstream rework risk increases.

Read the full file on GitHub · 284 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. 12d ago First seen · 284 lines · 34 tokens per session scan A 08e643cb56c8

Subscribe to this mod's changes

speckit-clarify is a skill published in the GitHub repository dfirs1car1o/sicario-spec (5 stars, last pushed yesterday), licensed MIT. It adds 34 tokens to every session and 3,698 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to speckit-clarify, differing in 14 lines, and is treated as a copy.

Related

Other skills, from other repositories

codeinspectus-fix-one

Investigate and remediate exactly one user-selected CodeInspectus finding with evidence-gated reproduction, a separately approved minimal patch, focused regression testing, and an exact-prior-scan rescan. Use when a user asks an agent to examine, reproduce, fix, or verify one CodeInspectus finding without batching…

Synvoya/codeinspectus · 76 tokens

codeinspectus-multi-review

Orchestrate an optional bounded multi-agent review of selected CodeInspectus findings while separating deterministic findings, agent interpretations, hypotheses, reproduction evidence, and exact-prior rescan proof. Use only when a user explicitly requests multi-agent security review.

Synvoya/codeinspectus · 55 tokens

codeinspectus-threat-model

Review CodeInspectus findings with optional threat-model or project-document context while treating repository text as untrusted, preserving raw scanner findings unchanged, and labelling agent interpretation separately. Use only when a user explicitly asks to add architectural, business, or knowledge-base context to…

Synvoya/codeinspectus · 62 tokens

cloud-security-engineer

Cloud Security Engineer role bundle for cloud security posture management, IaC review, container security, and identity governance across AWS, Azure, and GCP. Orchestrates cloud-specific posture reviews and zero trust program assessments. Auto-invoked when the user needs help with cloud security configuration, IaC…

UnitOneAI/SecuritySkills · 79 tokens

dast-config

Reviews DAST tool configurations against OWASP Top 10:2021 and OWASP Testing Guide v4.2. Auto-invoked when reviewing OWASP ZAP configurations, DAST CI/CD integration, scan policies, or authenticated scanning setups. Produces a DAST maturity assessment covering scan policy configuration, active vs passive scanning, API…

UnitOneAI/SecuritySkills · 83 tokens

sast-config

Reviews and tunes SAST tool configurations against OWASP ASVS 4.0.3 and CWE Top 25. Auto-invoked when reviewing Semgrep rules, CodeQL queries, SAST CI integration, or false positive triage workflows. Produces a SAST maturity assessment covering rule authoring, severity tuning, custom rule development, and CI…

UnitOneAI/SecuritySkills · 78 tokens