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/extract)<a href="https://agentmods.dev/commands/opsmill/infrahub-mcp/extract"><img src="https://agentmods.dev/badge/commands/opsmill/infrahub-mcp/extract/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/opsmill/infrahub-mcp/extract"><img src="https://agentmods.dev/badge/commands/opsmill/infrahub-mcp/extract.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.00021 | $0.03190 |
| Opus 5.5 | $0.00008 | $0.01276 |
| Sonnet 5.5 | $0.00004 | $0.00638 |
| Haiku 4.5 | $0.00002 | $0.00319 |
Grade A, and why
extract 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 2mo 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
98% identical to speckit.extract.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 — 341 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Input
$ARGUMENTS
You MUST consider the user input before proceeding (if not empty).
Outline
Goal: Analyze one or more completed spec directories and extract durable knowledge into the project's documentation system (dev/knowledge/, dev/guidelines/, dev/adr/), then mark each spec as extracted.
This command accepts multiple specs as input (space-separated) and processes them sequentially. It operationalizes the documentation lifecycle: specs/ → knowledge/ or guidelines/ (see dev/guidelines/markdown.md).
Phase 0: Setup & Validation
-
Parse arguments — split
$ARGUMENTSinto individual spec identifiers (space-separated). If$ARGUMENTSis empty, list available spec directories and ask the user to pick one or more. -
Resolve each spec directory:
- For each identifier in the arguments:
- If it matches
specs/NNN-*orNNN-*, resolve toREPO_ROOT/specs/NNN-* - If it is a bare name like
graphql-name-lookup, searchspecs/for a matching directory - If no match found for an identifier, report it and continue resolving the rest
- If it matches
- If no identifiers could be resolved, list available spec directories and ask the user to pick
- For each identifier in the arguments:
-
Validate each resolved spec:
spec.mdMUST exist — skip that spec with an error if missingresearch.mdSHOULD exist — warn if missing ("No ADRs can be extracted without research.md") but continue
-
Check extraction status for each spec:
- If
EXTRACTED.mdexists in the spec directory, warn the user that this spec was previously extracted - Also check if the spec already lives under
specs/archive/— if so, it was previously extracted and archived - Ask for confirmation before re-extracting — default is abort
- The user can choose to skip individual specs from the batch
- If
-
Summarize resolved specs — before proceeding, print the list of specs that will be processed:
Processing N spec(s): 1. specs/<spec-name-1> 2. specs/<spec-name-2> ...
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.
- 2mo ago First seen · 341 lines · 21 tokens per session scan A 0bbb4452648c
extract is a command published in the GitHub repository opsmill/infrahub-mcp (10 stars, last pushed 3d ago), licensed Apache-2.0. It adds 21 tokens to every session and 3,190 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 98% identical to speckit.extract.run, differing in 7 lines, and is treated as a copy.
Other commands, from other repositories
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.
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.
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.