What is speckit-opsmill-extract?

A documentation tool that extracts reusable knowledge, guidelines, and architecture decisions from completed project specifications. An ADR is a written record of an important technical decision and its reasoning.

It is for moving durable information into shared project documentation and marking the source specifications as processed.

It prevents useful decisions and lessons from being buried in finished project folders.

speckit-opsmill-extract — 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-opsmill-extract

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-opsmill-extract/github.svg)](https://agentmods.dev/skills/opsmill/infrahub-mcp/speckit-opsmill-extract)

Your own site

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

Your own site · 80×15

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

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

When invoked 3,295 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.

Origin 97% copy Near-identical to another mod 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.00030	$0.03295
Opus 5	$0.00015	$0.01648
Sonnet 5	$0.00006	$0.00659
Haiku 4.5	$0.00003	$0.00330

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

Security

Grade A, and why

speckit-opsmill-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 5d 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

This is a copy

97% identical to speckit-extract-run — 20 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.

.agents/skills/speckit-opsmill-extract/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.

5d ago First seen · 346 lines · 30 tokens per session scan A bec93f01cc15

Subscribe to this mod's changes

speckit-opsmill-extract is a skill published in the GitHub repository opsmill/infrahub-mcp (10 stars, last pushed 2d ago), licensed Apache-2.0. It adds 30 tokens to every session and 3,295 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to speckit-extract-run, differing in 20 lines, and is treated as a copy.

LLM Project management Writing and docs agent ai coding-agent infrahub infrastructure

stale-sweep

Sweep the googleapis/mcp-toolbox repo for issues and PRs with no real activity in N days (default 60), sort each by whose silence it is (the author's, ours, or nobody's), and draft the nudge or close comment. Use whenever a maintainer asks for a stale sweep, backlog cleanup, or an SLO check, e.g. "stale sweep", "find…

googleapis/mcp-toolbox · 159 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

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

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.