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.checklist.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.checklist)<a href="https://agentmods.dev/commands/rshade/mcp-devtools-server/speckit.checklist"><img src="https://agentmods.dev/badge/commands/rshade/mcp-devtools-server/speckit.checklist.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.03753 |
| Opus 5 | $0.00000 | $0.01877 |
| Sonnet 5 | $0.00000 | $0.00751 |
| Haiku 4.5 | $0.00000 | $0.00375 |
Grade A, and why
speckit.checklist 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
88% identical to checklist — 113 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 — 299 lines — stays where its author put it; the contents beside it link to each section on GitHub.
description = "Generate a custom checklist for the current feature based on user requirements."
prompt = """
description: Generate a custom checklist for the current feature based on user requirements.
Checklist Purpose: "Unit Tests for English"
CRITICAL CONCEPT: Checklists are UNIT TESTS FOR REQUIREMENTS WRITING - they validate the quality, clarity, and completeness of requirements in a given domain.
NOT for verification/testing:
- ❌ NOT "Verify the button clicks correctly"
- ❌ NOT "Test error handling works"
- ❌ NOT "Confirm the API returns 200"
- ❌ NOT checking if code/implementation matches the spec
FOR requirements quality validation:
- ✅ "Are visual hierarchy requirements defined for all card types?" (completeness)
- ✅ "Is 'prominent display' quantified with specific sizing/positioning?" (clarity)
- ✅ "Are hover state requirements consistent across all interactive elements?" (consistency)
- ✅ "Are accessibility requirements defined for keyboard navigation?" (coverage)
- ✅ "Does the spec define what happens when logo image fails to load?" (edge cases)
Metaphor: If your spec is code written in English, the checklist is its unit test suite. You're testing whether the requirements are well-written, complete, unambiguous, and ready for implementation - NOT whether the implementation works.
User Input
$ARGUMENTS
You MUST consider the user input before proceeding (if not empty).
Execution Steps
-
Setup: Run
.specify/scripts/bash/check-prerequisites.sh --jsonfrom repo root and parse JSON for FEATURE_DIR and AVAILABLE_DOCS list.- All file paths must be absolute.
- 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").
-
Clarify intent (dynamic): Derive up to THREE initial contextual clarifying questions (no pre-baked catalog). They MUST:
- Be generated from the user's phrasing + extracted signals from spec/plan/tasks
- Only ask about information that materially changes checklist content
- Be skipped individually if already unambiguous in
$ARGUMENTS - Prefer precision over breadth
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 · 299 lines · 0 tokens per session scan A b5247f37a85f
speckit.checklist 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 3,753 tokens. A static security scan graded it A with 0 findings. It is 88% identical to checklist, differing in 113 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.