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 commands/opsmill/infrahub-mcp/speckit.archivegit clone --depth 1 https://github.com/opsmill/infrahub-mcpWrote 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/opsmill/infrahub-mcp/speckit.archive)<a href="https://agentmods.dev/commands/opsmill/infrahub-mcp/speckit.archive"><img src="https://agentmods.dev/badge/commands/opsmill/infrahub-mcp/speckit.archive.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.00015 | $0.03964 |
| Opus 5 | $0.00008 | $0.01982 |
| Sonnet 5 | $0.00003 | $0.00793 |
| Haiku 4.5 | $0.00002 | $0.00396 |
Grade A, and why
speckit.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 6d 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- speckit.archive.run — 100% identical, 0 lines differ
- archive — 92% identical, 18 lines differ
How it starts
The opening of the file, as written. The whole thing — 432 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.
User Input
$ARGUMENTS
You MUST consider the user input before proceeding (if not empty).
Input Parsing
Parse $ARGUMENTS as follows:
- First token: feature spec directory path (e.g.,
specs/007-invoice-settings) - Remaining tokens: scope modifiers (optional, space-separated)
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 knowledge file (GEMINI.md / AGENTS.md / CLAUDE.md)
If $ARGUMENTS is empty, output ERROR: No feature spec directory provided. Usage: /speckit.archive.run specs/###-feature-name [--scope-modifier] and stop.
Step 0: Setup & Validation (Gate)
0.1 Resolve Paths
Run .specify/scripts/bash/check-prerequisites.sh --json --paths-only to identify the active feature directory and its artifacts. This script is mandatory for path discovery. If the script is missing, stop and inform the user.
Derive absolute paths for:
REPO_ROOT(from.specify/scripts/bash/check-prerequisites.sh --json --paths-onlyoutput)FEATURE_DIR(from.specify/scripts/bash/check-prerequisites.sh --json --paths-onlyoutput)MEMORY_DIR(REPO_ROOT / .specify/memory)TEMPLATES_DIR(REPO_ROOT / .specify/templates)
Path convention: Feature specs live in specs/{###-feature-name}/ at repo root. Use absolute paths for all file operations.
0.2 Validate Feature Directory
Verify FEATURE_DIR exists and contains:
spec.md(required)plan.md(required)
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.
- 6d ago First seen · 432 lines · 15 tokens per session scan A b188c3b7850d
speckit.archive is a command published in the GitHub repository opsmill/infrahub-mcp (10 stars, last pushed yesterday), licensed Apache-2.0. It adds 15 tokens to every session and 3,964 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 commands, from other repositories
save-memory
You are saving what you learned this session into the megamemory knowledge graph. This is YOUR memory — record anything valuable for future sessions: what you understood about the project, what you built, decisions that were made, patterns you noticed, or intent the user shared.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.