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 skills add stefaniuk/loadout --skill spec-consolidationgit 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/spec-consolidation)<a href="https://agentmods.dev/skills/stefaniuk/loadout/spec-consolidation"><img src="https://agentmods.dev/badge/skills/stefaniuk/loadout/spec-consolidation.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.00040 | $0.03614 |
| Opus 5 | $0.00020 | $0.01807 |
| Sonnet 5 | $0.00008 | $0.00723 |
| Haiku 4.5 | $0.00004 | $0.00361 |
Grade A, and why
spec-consolidation 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 8d 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 — 298 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec Consolidation Skill
This skill derives a product-facing view from the multi-feature Spec Kit
layout (specs/001-*/, specs/002-*/, specs/003-*/, …) into a single
intent-driven specification set under specs/product/.
Spec Kit is branch-first: each specs/NNN-* directory is a durable record of
one change. This skill does not replace that history. It produces a
derived product read-model for teams that need one consolidated intent view
across shipped or in-flight behaviour.
It is non-destructive: per-feature directories remain on disk as the canonical feature history unless the operator makes a separate archival decision later.
Why this exists
The repository follows spec-driven development
(spec → clarify → plan → tasks → implement). After several features
ship, the specs/ tree accumulates:
- Multiple
spec.mdfiles describing slices of the same product. - Stale
plan.mdandtasks.mdfiles reflecting how work was scheduled, not what the system now does. - Duplicated
data-model.md,research.md, andquickstart.mdcontent with partial overlaps and contradictions.
This skill produces a single, code-true, intent-only spec set. The discarded
artefact types (plan.md, tasks.md) do not belong in the final product set.
In Spec Kit, plan.md is still a technical design artefact, so it may be
consulted narrowly during reconciliation when that context is missing from
research.md, data-model.md, quickstart.md, or contracts/.
Output Layout
specs/product/
├── spec.md # Single product specification (intent only)
├── data-model.md # Consolidated domain model
├── research.md # Consolidated decisions and trade-offs (links ADRs)
├── quickstart.md # Unified operator quickstart
├── contracts/ # Merged or derived contract files (CLI, API, schemas, …)
└── checklists/ # Optional merged review checklists (deduplicated)
The numeric per-feature directories under specs/NNN-*/ are left in place.
The skill writes an index document under specs/product/ pointing to the
consolidated set, the baseline used, and the source feature directories that
fed each artefact.
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 298 lines · 40 tokens per session scan A 1536beb1c97a
spec-consolidation is a skill published in the GitHub repository stefaniuk/loadout (1 stars, last pushed 5d ago), licensed MIT. It adds 40 tokens to every session and 3,614 once invoked, about $0.0002 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.