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.tasks.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.tasks)<a href="https://agentmods.dev/commands/notmyself/claude-win11-speckit-update-skill/speckit.tasks"><img src="https://agentmods.dev/badge/commands/notmyself/claude-win11-speckit-update-skill/speckit.tasks/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.tasks"><img src="https://agentmods.dev/badge/commands/notmyself/claude-win11-speckit-update-skill/speckit.tasks.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.00018 | $0.01439 |
| Opus 5 | $0.00009 | $0.00720 |
| Sonnet 5 | $0.00004 | $0.00288 |
| Haiku 4.5 | $0.00002 | $0.00144 |
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 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
91% identical to speckit.tasks — 19 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 — 129 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
-
Setup: Run
.specify/scripts/powershell/check-prerequisites.ps1 -Jsonfrom repo root and parse FEATURE_DIR and AVAILABLE_DOCS list. All 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"). -
Load design documents: Read from FEATURE_DIR:
- Required: plan.md (tech stack, libraries, structure), spec.md (user stories with priorities)
- Optional: data-model.md (entities), contracts/ (API endpoints), research.md (decisions), quickstart.md (test scenarios)
- Note: Not all projects have all documents. Generate tasks based on what's available.
-
Execute task generation workflow:
- Load plan.md and extract tech stack, libraries, project structure
- Load spec.md and extract user stories with their priorities (P1, P2, P3, etc.)
- If data-model.md exists: Extract entities and map to user stories
- If contracts/ exists: Map endpoints to user stories
- If research.md exists: Extract decisions for setup tasks
- Generate tasks organized by user story (see Task Generation Rules below)
- Generate dependency graph showing user story completion order
- Create parallel execution examples per user story
- Validate task completeness (each user story has all needed tasks, independently testable)
-
Generate tasks.md: Use
.specify.specify/templates/tasks-template.mdas structure, fill with:- Correct feature name from plan.md
- Phase 1: Setup tasks (project initialization)
- Phase 2: Foundational tasks (blocking prerequisites for all user stories)
- Phase 3+: One phase per user story (in priority order from spec.md)
- Each phase includes: story goal, independent test criteria, tests (if requested), implementation tasks
- Final Phase: Polish & cross-cutting concerns
- All tasks must follow the strict checklist format (see Task Generation Rules below)
- Clear file paths for each task
- Dependencies section showing story completion order
- Parallel execution examples per story
- Implementation strategy section (MVP first, incremental delivery)
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 · 129 lines · 18 tokens per session scan A a4197b7dd5a3
speckit.tasks is a command published in the GitHub repository NotMyself/claude-win11-speckit-update-skill (30 stars, last pushed 10mo ago), licensed MIT. It adds 18 tokens to every session and 1,439 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to speckit.tasks, differing in 19 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.