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.tasksgit clone --depth 1 https://github.com/pilotspace/pilot-spaceWrote 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/pilotspace/pilot-space/speckit.tasks)<a href="https://agentmods.dev/commands/pilotspace/pilot-space/speckit.tasks"><img src="https://agentmods.dev/badge/commands/pilotspace/pilot-space/speckit.tasks.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 | $0.00018 | $0.01072 |
| Opus 5 | $0.00009 | $0.00536 |
| Sonnet 5 | $0.00004 | $0.00214 |
| Haiku 4.5 | $0.00002 | $0.00107 |
Grade A, and why
speckit.tasks 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.
How it starts
The opening of the file, as written. The whole thing — 150 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 to understand project rules.
Workflow
1. Setup
Run from repo root:
.specify/scripts/bash/check-prerequisites.sh --json
Parse FEATURE_DIR and AVAILABLE_DOCS from output. Use absolute paths throughout.
For arguments with single quotes (e.g., "I'm Groot"), use: 'I'\''m Groot' or "I'm Groot"
2. Load Design Documents
Read from FEATURE_DIR:
| Document | Required | Contains |
|---|---|---|
| plan.md | Yes | Tech stack, libraries, structure |
| spec.md | Yes | User stories with priorities (P1, P2, P3) |
| data-model.md | No | Entities to map to user stories |
| contracts/ | No | API endpoints to map to user stories |
| research.md | No | Decisions for setup tasks |
| quickstart.md | No | Test scenarios |
Generate tasks based on available documents only.
3. Generate Tasks
- Extract tech stack and structure from plan.md
- Extract prioritized user stories from spec.md
- For each optional doc that exists:
- data-model.md: Map entities to user stories
- contracts/: Map endpoints to user stories
- research.md: Extract decisions for setup tasks
- Generate tasks organized by user story (see Task Format below)
- Create dependency graph showing story completion order
- Identify parallel execution opportunities per user story
- Validate: each user story has complete tasks and is independently testable
4. Write tasks.md
Use .specify/templates/tasks-template.md as structure template.
Required sections:
- Feature name from plan.md
- Phase 1: Setup (project initialization)
- Phase 2: Foundational (blocking prerequisites for all user stories)
- Phase 3+: One phase per user story in priority order
- Final Phase: Polish & cross-cutting concerns
Each user story phase includes:
- Story goal and independent test criteria
- Tests (only if requested in spec)
- Implementation tasks with file paths
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 · 150 lines · 18 tokens per session scan A 684473080f1a
speckit.tasks is a command published in the GitHub repository pilotspace/pilot-space (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 18 tokens to every session and 1,072 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
git
Git operations with intelligent commit messages and workflow optimization.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
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.