What is speckit-extract-run?

A documentation workflow that takes completed software specification folders and extracts lasting knowledge, guidelines, and architecture decision records. An architecture decision record is a short record of an important technical choice and why it was made.

Use it to process one or more completed specification directories and add their reusable information to project documentation.

It prevents useful decisions and lessons from remaining buried in finished specifications. It also marks processed specifications so the documentation work can be tracked.

speckit-extract-run — Skill for Claude Code by opsmill

Install

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.

Any agent

npx skills add opsmill/infrahub-mcp --skill speckit-extract-run

Clone the repo

git clone --depth 1 https://github.com/opsmill/infrahub-mcp

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/opsmill/infrahub-mcp/speckit-extract-run/github.svg)](https://agentmods.dev/skills/opsmill/infrahub-mcp/speckit-extract-run)

Your own site

<a href="https://agentmods.dev/skills/opsmill/infrahub-mcp/speckit-extract-run"><img src="https://agentmods.dev/badge/skills/opsmill/infrahub-mcp/speckit-extract-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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/opsmill/infrahub-mcp/speckit-extract-run"><img src="https://agentmods.dev/badge/skills/opsmill/infrahub-mcp/speckit-extract-run.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 28 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 3,235 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector warn 7 Sept 2026

SkillSpector: 1 finding, up to high

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

high Prompt Injection · line 228
Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.

Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

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.00028	$0.03235
Opus 5	$0.00014	$0.01618
Sonnet 5	$0.00006	$0.00647
Haiku 4.5	$0.00003	$0.00324

Measured 10d ago against content hash dedc7e8fbd08, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

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 10d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

speckit-opsmill-extract — 97% identical, 20 lines differ

.agents/skills/speckit-extract-run/SKILL.md · 346 lines

How it starts

The opening of the file, as written. The whole thing — 346 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 $ARGUMENTS into individual spec identifiers (space-separated). If $ARGUMENTS is 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-* or NNN-*, resolve to REPO_ROOT/specs/NNN-*
  - If it is a bare name like graphql-name-lookup, search specs/ for a matching directory
  - If no match found for an identifier, report it and continue resolving the rest
- If no identifiers could be resolved, list available spec directories and ask the user to pick
Validate each resolved spec:
- spec.md MUST exist — skip that spec with an error if missing
- research.md SHOULD exist — warn if missing ("No ADRs can be extracted without research.md") but continue
Check extraction status for each spec:
- If EXTRACTED.md exists 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
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>
...
```

Read the full file on GitHub · 346 lines

Changes

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.

10d ago First seen · 346 lines · 28 tokens per session scan A dedc7e8fbd08

Subscribe to this mod's changes

speckit-extract-run is a skill published in the GitHub repository opsmill/infrahub-mcp (10 stars, last pushed today), licensed Apache-2.0. It adds 28 tokens to every session and 3,235 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.

LLM Writing and docs agent ai coding-agent infrahub infrastructure

tensorpool-gpu-cloud

Safely inspect and operate TensorPool GPU clusters and jobs using the current tp CLI, with explicit approval before any billable or destructive action.

synthetic-sciences/openscience · 34 tokens

lambda-gpu-cloud

Safely inspect and operate Lambda Cloud GPU instances through the documented Cloud API and SSH, with explicit approval before billable or destructive actions.

synthetic-sciences/openscience · 32 tokens

runpod-gpu-cloud

Safely inspect and operate RunPod resources with runpodctl, live product data, and explicit approval before paid or destructive actions.

synthetic-sciences/openscience · 32 tokens

vast-ai-gpu-cloud

Safely inspect and operate Vast.ai marketplace instances with the vastai CLI, live offer data, and explicit approval before paid or destructive actions.

synthetic-sciences/openscience · 34 tokens

givemeanode-agent-compute

Operate GiveMeANode GPU nodes, batch jobs, storage, and rollout sandboxes through its connected MCP server with bounded spend, durable recovery, and explicit approval for paid or destructive actions.

synthetic-sciences/openscience · 46 tokens

gpt-image-gen

MUST read before generating images. Detailed prompt-crafting guide for gpt-image models, covering tool routing (native imagegeneration server tool vs the generateimage tool), prompt structure from subject to background, verbatim text rendering, anti-patterns, and the revisedprompt feedback loop for iteration.

code-yeongyu/senpi · 63 tokens