Borrowing it
Nothing to install: this file belongs to racecraft-lab/racecraft-plugins-public. 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/racecraft-lab/racecraft-plugins-public/main/.claude/skills/speckit-archive-run/SKILL.mdgit clone --depth 1 https://github.com/racecraft-lab/racecraft-plugins-publicWrote 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/racecraft-lab/racecraft-plugins-public/speckit-archive-run)<a href="https://agentmods.dev/skills/racecraft-lab/racecraft-plugins-public/speckit-archive-run"><img src="https://agentmods.dev/badge/skills/racecraft-lab/racecraft-plugins-public/speckit-archive-run/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/skills/racecraft-lab/racecraft-plugins-public/speckit-archive-run"><img src="https://agentmods.dev/badge/skills/racecraft-lab/racecraft-plugins-public/speckit-archive-run.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.00023 | $0.03154 |
| Opus 5 | $0.00012 | $0.01577 |
| Sonnet 5 | $0.00005 | $0.00631 |
| Haiku 4.5 | $0.00002 | $0.00315 |
Grade A, and why
speckit-archive-run 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
95% identical to speckit-archive-run — 7 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 — 437 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Archive Run Skill
Act as the Chief Software Architect, Documentation Maintainer, and release provenance auditor.
Your goal is to archive merged feature specifications into durable project memory while preserving enough provenance to recover raw spec artifacts from git later. This command also supports Archive Sweep mode, which identifies previously merged feature specs before a new SpecKit run starts.
User Input
$ARGUMENTS
You MUST consider the user input before proceeding.
Input Parsing
Parse $ARGUMENTS as shell-like tokens. Supported forms:
speckit.archive.run specs/###-feature-name [scope] [provenance] [mode]
speckit.archive.run --sweep --current-target specs/###-current-feature [provenance] [mode]
Positional Input
- First non-option token: feature spec directory path, for example
specs/007-invoice-settings. - In
--sweepmode, no positional feature directory is required.
Scope Modifiers
If none are provided, update all archival 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 knowledge file (GEMINI.md,AGENTS.md, orCLAUDE.md)
Mode And Safety Options
--dry-run: do not modify files; produce the same eligibility, provenance, and cleanup report that an apply run would use.--apply: apply memory archival edits. This is the default for a single feature archive unless--dry-runis present.--sweep: discover previously merged feature specs and report archive and cleanup eligibility before any new spec work begins.--apply-cleanup: after successful archival, remove or move completed spec folders out of activespecs/**only if every cleanup gate passes.--current-target <path>: active feature spec for the current run. Archive Sweep MUST exclude this path from archival and cleanup.
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 · 437 lines · 23 tokens per session scan A af96072b028d
speckit-archive-run is a skill published in the GitHub repository racecraft-lab/racecraft-plugins-public (5 stars, last pushed today), licensed MIT. It adds 23 tokens to every session and 3,154 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 95% identical to speckit-archive-run, differing in 7 lines, and is treated as a copy.
Other skills, from other repositories
context-engineering
Optimizes agent context setup. Use when starting a new session, when agent output quality degrades, when switching between tasks, or when you need to configure rules files and context for a project.
gsd-graphify
Build, query, and inspect the project knowledge graph in .planning/graphs/.
handoff
Prepare a clean cross-session handoff so the next agent can pick up where you left off. Writes a focused continue.md in the active slice dir and ensures STATE.md + summary artifacts are current. Use when asked to "hand off", "prepare handoff", "pause work", "bookmark this", "I'll come back to this later", before…
build-executor
Govern implementation from an approved execution contract. Invoke when execution-contract.md is approved and the user wants disciplined build work, TDD execution, or guarded batch-by-batch implementation.
workflow-start
Primary entry point for the spec-superflow state-machine workflow. Invoke when the user is inside an active spec-superflow change directory (look for .spec-superflow.yaml, changes/ /, proposal.md, specs/, design.md, tasks.md, or execution-contract.md) and asks to start, continue, resume, implement, plan, or figure out…
contract-builder
Convert approved planning artifacts into an execution contract. Invoke when the user wants to start building, asks to move from planning to implementation, or when execution-contract.md is missing or stale.