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-plannpx skills add stefaniuk/loadout --skill speckit-plangit 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-plan)<a href="https://agentmods.dev/skills/stefaniuk/loadout/speckit-plan"><img src="https://agentmods.dev/badge/skills/stefaniuk/loadout/speckit-plan.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.00019 | $0.02466 |
| Opus 5 | $0.00010 | $0.01233 |
| Sonnet 5 | $0.00004 | $0.00493 |
| Haiku 4.5 | $0.00002 | $0.00247 |
Grade A, and why
speckit-plan 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.
How it starts
The opening of the file, as written. The whole thing — 227 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 creating a development plan.
Workflow context:
- Input:
spec.md(feature specification) - Output:
plan.md(implementation plan) - Next phase: Tasks generation (
/speckit-tasks)
Base requirements: Follow all rules in copilot-instructions.md, particularly:
- Documentation ADRs
- Toolchain version
- Repository tooling
Show & Tell Sections (Mandatory)
Each phase and user story in plan.md must include a Show & Tell subsection. This subsection defines the demonstration steps that will be:
- Expanded with specific commands in
tasks.md(next phase) - Executed by the user during implementation to verify completion
AI Assistant Execution Requirement (Mandatory)
Show & Tell steps must be written so AI Assistant can execute and validate them without guessing.
- Use explicit, runnable commands, URLs, and API calls
- Include an expected result for every step (output text, status code, or visible UI state)
- Avoid vague language such as "check it works" or "verify manually"
- State pass/fail criteria clearly so steps cannot be skipped or missed during
/speckit-implement - For infrastructure, scripts, documentation, or reporting tools, prefer lightweight checks such as file presence, command exit status, or output schema/keys instead of app-style browser flows
During implementation, execute every Show & Tell step and confirm the expected result before marking the phase or user story complete.
- If a step fails because the implementation is wrong, fix it and re-run the step
- If a step fails because the environment is not ready, record the blocker, add the missing setup step, and re-run when the environment is ready
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 · 227 lines · 19 tokens per session scan A 700de1d906da
speckit-plan is a skill published in the GitHub repository stefaniuk/loadout (1 stars, last pushed 3d ago), licensed MIT. It adds 19 tokens to every session and 2,466 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 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.