speckit.specify

speckit.specify is a command for GitHub Copilot from alonf/specrew. It costs 0 tokens per session (257 once invoked), scanned A, original, MIT.

A Spec Kit command that gathers feature requirements through several structured viewpoints before writing a specification. It considers product, user experience, software architecture, and delivery planning concerns.

In plain words
What is it for?
Use it at the start of feature work to collect input and produce information for spec.md.
Why use it?
It helps expose unclear decisions and missing requirements before implementation planning begins. A user profile can adjust how deeply it asks about certain areas.

Command for GitHub Copilot

Written for GitHub Copilot: a Copilot chat mode or prompt. Also seen: agent in frontmatter.

Good fit Use it at the start of feature work to collect input and produce information for spec.md.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/alonf/specrew/speckit.specify
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/alonf/specrew

Made for: GitHub Copilot.

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/commands/alonf/specrew/speckit.specify/github.svg)](https://agentmods.dev/commands/alonf/specrew/speckit.specify)
Your own site
<a href="https://agentmods.dev/commands/alonf/specrew/speckit.specify"><img src="https://agentmods.dev/badge/commands/alonf/specrew/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/commands/alonf/specrew/speckit.specify"><img src="https://agentmods.dev/badge/commands/alonf/specrew/speckit.specify.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 257 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 original No closer match found 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.00000 $0.00257
Opus 5.5 $0.00000 $0.00103
Sonnet 5.5 $0.00000 $0.00051
Haiku 4.5 $0.00000 $0.00026

Measured 1mo ago against content hash 79c14b7504e5, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 1mo 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.

.github/prompts/speckit.specify.prompt.md · 18 lines

What it actually says

Persona-Driven Substantive Intake

Feature 049 Iteration 003: Before generating the specification, invoke the persona-driven intake engine:

pwsh -File extensions/specrew-speckit/scripts/intake/Invoke-SpecifyIntake.ps1 -UserInput "<feature description>"

The engine applies 4 sequential internal persona lenses (Product Manager, UX/UI Specialist, Architect, AI Researcher / Project Manager) covering 12 categories from each perspective. These lenses are Specrew internals — not identities the user holds. Question depth is driven by the current user's Crew Interaction Profile (decision-area settings: Product Strategy, UX/UI Design, Software Architecture, AI Delivery Planning) resolved from ~/.specrew/user-profile.yml ($env:USERPROFILE\.specrew\user-profile.yml on Windows). /speckit.specify is the only surface that hard-applies the profile; everywhere else it is soft session guidance only.

Fallback guidance: If uncertain about any requirement, choose "Other" or "I don't know, you decide" to trigger auto-decisions with transparency.

Use intake results to inform spec.md generation.

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. 1mo ago First seen · 18 lines · 0 tokens per session scan A 79c14b7504e5

Subscribe to this mod's changes

speckit.specify is a command published in the GitHub repository alonf/specrew (55 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 257 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-07.