Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/stn1slv/spec-kit-archivenpx agentmods add commands/stn1slv/spec-kit-archive/archiveWrote 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/stn1slv/spec-kit-archive/archive)<a href="https://agentmods.dev/commands/stn1slv/spec-kit-archive/archive"><img src="https://agentmods.dev/badge/commands/stn1slv/spec-kit-archive/archive/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/stn1slv/spec-kit-archive/archive"><img src="https://agentmods.dev/badge/commands/stn1slv/spec-kit-archive/archive.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.00015 | $0.34500 |
| Opus 5.5 | $0.00006 | $0.13800 |
| Sonnet 5.5 | $0.00003 | $0.06900 |
| Haiku 4.5 | $0.00002 | $0.03450 |
Grade A, and why
archive 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 25d 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 — 964 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Act as the Chief Software Architect and Documentation Maintainer.
A feature has been merged into the main branch. Your goal is to archive the feature specification into the main project memory — ensuring completeness, resolving conflicts, closing gaps, and respecting the project constitution.
Completeness means nothing is lost from the feature's own artifacts. It does not mean filling gaps from elsewhere. See Allowed Sources below, which bounds every step of this command.
User Input
$ARGUMENTS
You MUST consider the user input before proceeding (if not empty).
Input Parsing
This command archives exactly one feature per run. There is no batch or range mode. To archive several features, run the command once per feature in ascending feature order, so each run sees the result of the one before it.
Parse $ARGUMENTS as follows:
- First token: feature spec directory path. Spec-kit projects name these directories in more than one way, and all of them are valid here: sequential (
specs/007-invoice-settings), timestamped (specs/20260814-101500-invoice-settings, produced byspecifywith timestamp numbering), and nested under a scope directory (specs/billing/006-invoice-settings). Nothing in this command may key on a three-digit prefix. - Then: scope modifiers (optional,
--flags immediately after the path), followed by optional free-form guidance text
Supported scope modifiers (if none provided, update all artifacts):
--spec-only— update only.specify/memory/spec.md--plan-only— update only.specify/memory/plan.md--changelog-only— update only.specify/memory/changelog.md--agent-only— update only the agent context file(s), as discovered by Step 0.7; when a project keeps several in sync, this covers all of them
If several scope modifiers are supplied, the scope is their union — --spec-only --changelog-only updates both spec.md and changelog.md and nothing else. "Only" bounds the whole set, not each flag individually.
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.
- 25d ago Changed · +30 lines 0792123af15d
- 1mo ago First seen · 934 lines · 15 tokens per session scan A c01cdc6e748a
archive is a command published in the GitHub repository stn1slv/spec-kit-archive (30 stars, last pushed 25d ago), licensed MIT. It adds 15 tokens to every session and 34,500 once invoked, about $0.0001 per session on Opus 5.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-30.
Other commands, from other repositories
sddp-implement-qc-loop
Command description: Run implement and QC in a continuous loop. Argument hint: [optional: feature directory or branch name] Command category: orchestration Prerequisites: spec, plan, tasks.
sddp-qc
Command description: Run quality control against the implemented feature. Argument hint: [optional: testing focus such as unit tests, security audit, requirements sync] Command category: feature-delivery Prerequisites: spec, plan, tasks, implementation:complete.
sddp-checklist
Command description: Generate and evaluate a requirements quality checklist. Argument hint: [optional: quality focus or feature context] Command category: feature-delivery Prerequisites: spec, plan.
amazing-e2e-check
Run explicitly requested E2E, browser, device, or installed-deployment scenarios in an independent verification workflow.
api-runtime-verify
Verify a built backend HTTP surface at runtime: per route, record the response, assert it against the slice's acceptance behavior, and decide PASS/FAIL/BLOCKED. Do not use to review a contract before implementation (use api-contract-review or graphql-contract-review), write code (use implement-approved-slice), triage…
app-runtime-verify
Verify a mobile or app runtime: run the app (device, emulator, or headless), read captured output (logcat, iOS device log, or Metro/JS console), classify errors per stack, and decide a PASS/FAIL gate. Adapters: React Native/Expo, Unity mobile. Do not use to plan a screen (use implementation-plan), to write or fix code…