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 skills/stefaniuk/loadout/speckit-tasksnpx skills add stefaniuk/loadout --skill speckit-tasksgit clone --depth 1 https://github.com/stefaniuk/loadoutWrote 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/skills/stefaniuk/loadout/speckit-tasks)<a href="https://agentmods.dev/skills/stefaniuk/loadout/speckit-tasks"><img src="https://agentmods.dev/badge/skills/stefaniuk/loadout/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.1 | $0.00024 | $0.03156 |
| Opus 5 | $0.00012 | $0.01578 |
| Sonnet 5 | $0.00005 | $0.00631 |
| Haiku 4.5 | $0.00002 | $0.00316 |
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 5d 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
75% identical to speckit-tasks — 169 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 — 290 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workflow Mode Guard
Use this skill only when the active local workflow mode is speckit.
Before proceeding:
- Run
./scripts/hooks/workflow-mode.sh status. - If the active mode is
superpowers, stop and tell the user to switch withmake workflow-use mode=speckitor continue with the Superpowers workflow instead. - Do not mix
speckit-*commands with Superpowers workflow skills in the same session or worktree.
You MUST adhere to the following mandatory requirements when generating development tasks.
Workflow context:
- Input:
plan.md(implementation plan) - Output:
tasks.md(actionable task list) - Next phase: Implementation (
/speckit-implement)
Base requirements: Follow all rules in copilot-instructions.md, particularly:
- Repository tooling
- Test-driven development
- Repository verification policy
Feature Class Detection
This skill is best suited to multi-phase features with clear user stories, dependencies, and independently testable outcomes.
- For narrow repository-internal changes such as make targets, scripts, docs, or patch maintenance, keep the task structure deliberately small
- Do not invent extra phases, user stories, or contracts solely to mimic a larger application workflow
Show & Tell Sections (Mandatory)
Each phase and user story in tasks.md must include a Show & Tell subsection. Expand the outline from plan.md with specific executable steps:
- Terminal commands to run (with expected output)
- Browser URLs to navigate (if applicable)
- API calls to execute (if applicable)
- Screenshots or expected visual state (described)
These steps will be executed during implementation to verify each phase is complete.
AI Assistant Execution Requirement (Mandatory)
AI Assistant MUST execute every Show & Tell step during /speckit-implement and validate that the expected result is achieved.
- Do not allow placeholder or ambiguous steps
- Every step must include explicit pass/fail criteria
- If a step fails, update tasks and/or implementation, then re-run the step
- Do not mark a phase or user story complete until all Show & Tell steps pass
- For infrastructure, scripts, documentation, or reporting tools, lightweight Show & Tell steps are acceptable when they stay explicit and verifiable
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.
- 5d ago First seen · 290 lines · 24 tokens per session scan A 1f9f2f281cbf
speckit-tasks is a skill published in the GitHub repository stefaniuk/loadout (1 stars, last pushed 3d ago), licensed MIT. It adds 24 tokens to every session and 3,156 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 75% identical to speckit-tasks, differing in 169 lines, and is treated as a copy.
Other skills, from other repositories
artifact-conventions
Defines preservation, format, and section rules for SDD specification artifacts (spec.md, plan.md, tasks.md, checklists). Use when editing feature-artifact files under specs/ / to prevent accidental corruption of cross-referenced IDs, priorities, and gating state.
plan-authoring
Reference material for writing implementation plans (technical context, architecture decisions, data models, API contracts, project-instructions alignment). Loaded on demand by plan-feature; not directly invokable.
task-generation
Reference material with the canonical task-format grammar and decomposition rules for plan-to-tasks expansion. Loaded on demand by generate-tasks; not directly invokable.
adr-authoring
Defines the canonical MADR format, lifecycle rules, numbering policy, and SAD catalog contract for standalone ADRs under specs/adrs/.
implementation-standards
Reference material with coding standards (defensive coding, error handling, testing patterns). Loaded on demand by the Developer sub-agent (.github/agents/developer.md); not directly invokable.
spec-authoring
Reference material for writing product, technical, and operational specifications (work-item priorities, requirement families, success criteria). Loaded on demand by specify-feature; not directly invokable.