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.
npx agentmods add commands/pilotspace/pilot-space/speckit.implementgit clone --depth 1 https://github.com/pilotspace/pilot-spaceWhat 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 | $0.00014 | $0.02173 |
| Opus 5 | $0.00007 | $0.01086 |
| Sonnet 5 | $0.00003 | $0.00435 |
| Haiku 4.5 | $0.00001 | $0.00217 |
Grade A, and why
speckit.implement 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 271 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Input
$ARGUMENTS
Consider user input before proceeding (if not empty). Load @docs/dev-pattern/README.md for project rules.
Flags
| Flag | Description | Default |
|---|---|---|
--interactive |
Prompt for confirmations (checklist, failures) | false |
--stop-on-failure |
Halt on first task failure | false |
--skip-checklists |
Skip checklist validation entirely | false |
--phase {N} |
Execute specific phase only | all |
--task T{ID} |
Execute single task | all |
--dry-run |
Preview execution plan without changes | false |
Workflow
Phase 1: Prerequisites
Run .specify/scripts/bash/check-prerequisites.sh --json --require-tasks --include-tasks from repo root.
Parse JSON for FEATURE_DIR and AVAILABLE_DOCS (use absolute paths).
For single quotes in args like "I'm Groot", use escape syntax: 'I'\''m Groot' or double-quote.
Phase 2: Checklist Validation
Skip this phase if --skip-checklists flag is set or FEATURE_DIR/checklists/ does not exist.
Scan checklist files:
- Count total items: Lines matching
- [ ]or- [X]or- [x] - Count completed: Lines matching
- [X]or- [x] - Count incomplete: Lines matching
- [ ]
Display status table:
| Checklist | Total | Completed | Incomplete | Status |
|-------------|-------|-----------|------------|----------|
| ux.md | 12 | 12 | 0 | PASS |
| test.md | 8 | 5 | 3 | FAIL |
| security.md | 6 | 6 | 0 | PASS |
Behavior:
| Condition | Default (automatic) | With --interactive |
|---|---|---|
| All checklists complete | Proceed to Phase 3 | Proceed to Phase 3 |
| Some checklists incomplete | Log warning, proceed | Ask user confirmation |
Warning format (automatic mode):
Proceeding with incomplete checklists (use --interactive to prompt)
Phase 3: Load Context
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.
- 2d ago First seen · 271 lines · 14 tokens per session scan A a25f100aa0db
speckit.implement is a command published in the GitHub repository pilotspace/pilot-space (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 14 tokens to every session and 2,173 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-31.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
speckit.auto
Automatically execute the four core phases of the Spec-Driven Development (SDD) pipeline: specify → plan → tasks → implement, in strict sequential order.
daily-priorities
Query DIGI Jira via the Atlassian MCP to build a prioritized daily work plan. The report has two parts: suggested priorities (the recommendation) and full context (everything you need to evaluate whether the suggestions are right and what else is on the docket).
OPSX: Bulk Archive
Archive multiple completed changes at once.
sync-linear
Sync current work with Linear ticket status.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).