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.extract.rungit 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.extract.run)<a href="https://agentmods.dev/commands/opsmill/infrahub-mcp/speckit.extract.run"><img src="https://agentmods.dev/badge/commands/opsmill/infrahub-mcp/speckit.extract.run.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.00021 | $0.03209 |
| Opus 5 | $0.00010 | $0.01605 |
| Sonnet 5 | $0.00004 | $0.00642 |
| Haiku 4.5 | $0.00002 | $0.00321 |
Grade A, and why
speckit.extract.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 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:
- extract — 98% identical, 7 lines differ
- speckit.opsmill.extract — 97% identical, 20 lines differ
How it starts
The opening of the file, as written. The whole thing — 344 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
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 · 344 lines · 21 tokens per session scan A c41ae13c29cf
speckit.extract.run is a command published in the GitHub repository opsmill/infrahub-mcp (10 stars, last pushed yesterday), licensed Apache-2.0. It adds 21 tokens to every session and 3,209 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
awesome-chatgpt
Search awesome-ChatGPT-repositories for open-source GitHub repositories related to ChatGPT and LLMs.
AGENTS
Per-command agent-optimized usage and structure guide.
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.
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.