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.
git 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/archive)<a href="https://agentmods.dev/commands/opsmill/infrahub-mcp/archive"><img src="https://agentmods.dev/badge/commands/opsmill/infrahub-mcp/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.03905 |
| Opus 5 | $0.00008 | $0.01953 |
| Sonnet 5 | $0.00003 | $0.00781 |
| Haiku 4.5 | $0.00002 | $0.00391 |
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 3d 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
92% identical to speckit.archive — 18 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 — 428 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 {SCRIPT} 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{SCRIPT}output)FEATURE_DIR(from{SCRIPT}output)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)
If any required file is missing:
⚠️ Invalid feature spec: Missing required files in
FEATURE_DIR. Expected:
- spec.md
- plan.md
Run
/speckit.specifyand/speckit.planfirst.
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.
- 3d ago First seen · 428 lines · 15 tokens per session scan A cfdba2803824
archive is a command published in the GitHub repository opsmill/infrahub-mcp (10 stars, last pushed 2d ago), licensed Apache-2.0. It adds 15 tokens to every session and 3,905 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to speckit.archive, differing in 18 lines, and is treated as a copy.
Other commands, from other repositories
hep-graph.body
A command for viewing saved Agentlas automation graphs and requesting that one be run. The desktop app performs the actual run.
fire-execute-plan
Execute a single plan with segment-based routing, per-task atomic commits, and test enforcement.
bootstrap-memory
RUN { git ls-files; git ls-files --others --exclude-standard; } 2>/dev/null | sort -u | xargs wc -l 2>/dev/null | sort -rn | head -150 READ README.md.
tree
Emit a compact indented view of the active task hierarchy and refresh state/task-tree.json. This is the primary tool for understanding the board's shape before adding new work.
pm-review-user-01-happy
Un PRD est disponible dans output/. Le wiki contient des pages persona- et interview- avec des verbatims. Le pm-user-advocate vérifie l'alignement du PRD avec les personas, identifie les personas non servis, cite les verbatims contradictoires, et évalue le niveau de confiance de chaque claim. Une page type…
create-story
Create the next user story from epics+stories with enhanced context analysis and direct ready-for-dev marking.