Borrowing it
Nothing to install: this file belongs to rshade/mcp-devtools-server. 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/rshade/mcp-devtools-server/main/.gemini/commands/speckit.specify.tomlgit clone --depth 1 https://github.com/rshade/mcp-devtools-serverWrote 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/rshade/mcp-devtools-server/speckit.specify)<a href="https://agentmods.dev/commands/rshade/mcp-devtools-server/speckit.specify"><img src="https://agentmods.dev/badge/commands/rshade/mcp-devtools-server/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.00000 | $0.02819 |
| Opus 5 | $0.00000 | $0.01409 |
| Sonnet 5 | $0.00000 | $0.00564 |
| Haiku 4.5 | $0.00000 | $0.00282 |
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 3d 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
73% 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 — 262 lines — stays where its author put it; the contents beside it link to each section on GitHub.
description = "Create or update the feature specification from a natural language feature description."
prompt = """
description: Create or update the feature specification from a natural language feature description. handoffs:
- label: Build Technical Plan agent: speckit.plan prompt: Create a plan for the spec. I am building with...
- label: Clarify Spec Requirements agent: speckit.clarify prompt: Clarify specification requirements send: true
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 {{args}} 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"
-
Check for existing branches before creating new one:
a. First, fetch all remote branches to ensure we have the latest information:
git fetch --all --pruneb. Find the highest feature number across all sources for the short-name:
- Remote branches:
git ls-remote --heads origin | grep -E 'refs/heads/[0-9]+-<short-name>$' - Local branches:
git branch | grep -E '^[* ]*[0-9]+-<short-name>$' - Specs directories: Check for directories matching
specs/[0-9]+-<short-name>
- Remote branches:
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.
- 3d ago First seen · 262 lines · 0 tokens per session scan A b5d277711153
speckit.specify is a command published in the GitHub repository rshade/mcp-devtools-server (5 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 2,819 tokens. A static security scan graded it A with 0 findings. It is 73% identical to specify, differing in 208 lines, and is treated as a copy.
Other commands, from other repositories
backlog
The project layer: milestones, epics, and user stories with refusing controllers — spec-seeded, sprint-ready.
sprint
Scope-boxed sprints over the backlog: one active sprint, explicit carry-over, a close that refuses to hide unfinished work.
status
The state of play, computed fresh: branch, dirty files, the active sprint, open work, index freshness.
triage_stale.spec
Task: t-1355 Command: brana backlog triage-stale.
forge
Ore in, steel out. Full pipeline: plan → execute → verify. Use: /forge 'task', /forge --full, --discuss, --plan-only, --execute, --park, --resume.
beads
Beads task tracker integration for SDP workflows.