Borrowing it
Nothing to install: this file belongs to fstandhartinger/ralph-wiggum. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/fstandhartinger/ralph-wiggum/main/.cursor/commands/speckit.specify.mdgit clone --depth 1 https://github.com/fstandhartinger/ralph-wiggumWrote 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.
[](https://agentmods.dev/commands/fstandhartinger/ralph-wiggum/speckit.specify)<a href="https://agentmods.dev/commands/fstandhartinger/ralph-wiggum/speckit.specify"><img src="https://agentmods.dev/badge/commands/fstandhartinger/ralph-wiggum/speckit.specify.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00012 | $0.00453 |
| Opus 5 | $0.00006 | $0.00227 |
| Sonnet 5 | $0.00002 | $0.00091 |
| Haiku 4.5 | $0.00001 | $0.00045 |
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 8d 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.
What it actually says
User Input
$ARGUMENTS
You MUST consider the user input before proceeding (if not empty).
Outline
The text after /speckit.specify is the feature description. Do not ask the user to repeat it unless it is empty.
Given that description, do this:
-
Generate a concise short name (2-4 words) for the spec folder:
- Extract the most meaningful keywords
- Use action-noun format when possible (e.g., "user-auth", "billing-dashboard")
- Preserve technical terms and acronyms (OAuth2, JWT, API)
-
Determine the next spec number (NO BRANCH CREATION):
a. List existing spec directories:
ls -d specs/[0-9]*/ 2>/dev/null | sort -t/ -k2 -nb. Find the highest number N and use N+1 (zero-padded to 3 digits)
c. Create the spec directory structure:
mkdir -p specs/NNN-short-name/checklistsd. Set SPEC_FILE =
specs/NNN-short-name/spec.md -
Load
templates/spec-template.mdto understand required sections. -
Write the spec using the template structure, replacing placeholders with concrete details derived from the feature description while preserving section order and headings.
-
Completion Signal: Ensure the spec includes a
## Completion Signalsection with:- Implementation checklist
- Testing requirements
- Iteration instructions
- Completion promise (
<promise>DONE</promise>)
-
Create a quality checklist at
specs/NNN-short-name/checklists/requirements.mdusingtemplates/checklist-template.md. -
If anything is ambiguous, add up to 3
[NEEDS CLARIFICATION: ...]markers in the spec. For each marker, present a clear question and suggested answers.
Output
Return: SUCCESS (spec ready for implementation via Ralph Wiggum)
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.
- 8d ago First seen · 57 lines · 12 tokens per session scan A dc8233ae9541
speckit.specify is a command published in the GitHub repository fstandhartinger/ralph-wiggum (292 stars, last pushed 3mo ago), licensed MIT. It adds 12 tokens to every session and 453 once invoked, about $0.0001 per session on Opus 5. 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-08-30.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.