Borrowing it
Nothing to install: this file belongs to NotMyself/claude-win11-speckit-update-skill. 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/NotMyself/claude-win11-speckit-update-skill/main/.claude/commands/speckit.specify.mdgit clone --depth 1 https://github.com/NotMyself/claude-win11-speckit-update-skillWrote 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/notmyself/claude-win11-speckit-update-skill/speckit.specify)<a href="https://agentmods.dev/commands/notmyself/claude-win11-speckit-update-skill/speckit.specify"><img src="https://agentmods.dev/badge/commands/notmyself/claude-win11-speckit-update-skill/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.
<a href="https://agentmods.dev/commands/notmyself/claude-win11-speckit-update-skill/speckit.specify"><img src="https://agentmods.dev/badge/commands/notmyself/claude-win11-speckit-update-skill/speckit.specify.svg" alt="Reviewed on agentmods" width="80" 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.00013 | $0.02474 |
| Opus 5 | $0.00006 | $0.01237 |
| Sonnet 5 | $0.00003 | $0.00495 |
| Haiku 4.5 | $0.00001 | $0.00247 |
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 11d 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.
This is a copy
66% identical to specify — 208 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.
How it starts
The opening of the file, as written. The whole thing — 230 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).
Outline
The text the user typed after /speckit.specify in the triggering message is the feature description. Assume you always have it available in this conversation even if $ARGUMENTS appears literally below. Do not ask the user to repeat it unless they provided an empty command.
Given that feature description, do this:
-
Generate a concise short name (2-4 words) for the branch:
- Analyze the feature description and extract the most meaningful keywords
- Create a 2-4 word short name that captures the essence of the feature
- Use action-noun format when possible (e.g., "add-user-auth", "fix-payment-bug")
- Preserve technical terms and acronyms (OAuth2, API, JWT, etc.)
- Keep it concise but descriptive enough to understand the feature at a glance
- Examples:
- "I want to add user authentication" → "user-auth"
- "Implement OAuth2 integration for the API" → "oauth2-api-integration"
- "Create a dashboard for analytics" → "analytics-dashboard"
- "Fix payment processing timeout bug" → "fix-payment-timeout"
-
Run the script
.specify/scripts/powershell/create-new-feature.ps1 -Json "$ARGUMENTS"from repo root with the short-name argument and parse its JSON output for BRANCH_NAME and SPEC_FILE. All file paths must be absolute.IMPORTANT:
- Append the short-name argument to the
.specify/scripts/powershell/create-new-feature.ps1 -Json "$ARGUMENTS"command with the 2-4 word short name you created in step 1 - Bash:
--short-name "your-generated-short-name" - PowerShell:
-ShortName "your-generated-short-name" - For single quotes in args like "I'm Groot", use escape syntax: e.g 'I'''m Groot' (or double-quote if possible: "I'm Groot")
- You must only ever run this script once
- The JSON is provided in the terminal as output - always refer to it to get the actual content you're looking for
- Append the short-name argument to the
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.
- 11d ago First seen · 230 lines · 13 tokens per session scan A 9f929ed47dae
speckit.specify is a command published in the GitHub repository NotMyself/claude-win11-speckit-update-skill (30 stars, last pushed 10mo ago), licensed MIT. It adds 13 tokens to every session and 2,474 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 66% identical to specify, differing in 208 lines, and is treated as a copy.
Other commands, from other repositories
trex.project.init
Validate that this TRex-spawned project is in a healthy, working state. This command is idempotent — it succeeds if everything is already running and correct, and only fails if something is genuinely broken.
trex.kind.add-field
Add a new field to an existing Kind, updating all layers consistently.
trex.kind.new
Generate a complete CRUD entity (Kind) using the automated generator script.
trex.test.integration
Run integration tests against a real PostgreSQL database (provisioned automatically via testcontainers).
trex.db.setup
Start a fresh PostgreSQL container and run all migrations. If a database already exists, this will tear it down first.
trex.verify
Run all static analysis checks: go vet, format verification, and linting.