infrahub-mcp: Command for Claude Code

.specify/extensions/iterate/commands/define.md

define is a command for Claude Code from opsmill/infrahub-mcp. It costs 28 tokens per session (2,309 once invoked), scanned C, a copy of speckit.iterate.define, Apache-2.0.

A command that analyzes a requested change against the current feature documents and implementation progress, then writes a reviewable iteration plan. It records the plan without changing the existing specifications.

In plain words
What is it for?
Use it to define additions, modifications, or removals for a feature or phase and save the proposed work in a pending iteration document.
Why use it?
It gives changes a clear, reviewable proposal before they alter project documents or implementation work.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

This is opsmill/infrahub-mcp's own configuration. It tells Claude Code how to work on infrahub-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything infrahub-mcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to opsmill/infrahub-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/opsmill/infrahub-mcp/stable/.specify/extensions/iterate/commands/define.md
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.

agentmods badge for define

README.md
[![agentmods](https://agentmods.dev/badge/commands/opsmill/infrahub-mcp/define.svg)](https://agentmods.dev/commands/opsmill/infrahub-mcp/define)
Your own site
<a href="https://agentmods.dev/commands/opsmill/infrahub-mcp/define"><img src="https://agentmods.dev/badge/commands/opsmill/infrahub-mcp/define.svg" alt="Measured on agentmods" height="20"></a>
Per session 28 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,309 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00028 $0.02309
Opus 5 $0.00014 $0.01154
Sonnet 5 $0.00006 $0.00462
Haiku 4.5 $0.00003 $0.00231

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

Security

Grade C, and why

define scanned grade C with 1 finding 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 4d 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.

Tells the agent never to refusehighAnti-refusal

Suppressing the ability to decline removes a core safety control; a later harmful request then succeeds.

- **Preserve completed work by default** — flag risks when completed tasks are affected, but don't refuse the iteration. The user decides.
Origin

This is a copy

97% identical to speckit.iterate.define — 16 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.

.specify/extensions/iterate/commands/define.md · 260 lines

How it starts

The opening of the file, as written. The whole thing — 260 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).

The text the user typed after /speckit.iterate.define is the change request. It describes what should be added, modified, or removed from the current feature — either the whole feature or a specific phase/subtask.

Outline

Goal: Analyze a requested change against the feature's current spec state and implementation progress, then produce a reviewable iteration plan written to pending-iteration.md. This command does not modify any spec artifacts — it only writes the pending iteration file.

1. Initialize Feature Context

Run .specify/scripts/bash/check-prerequisites.sh --json --paths-only from repo root once. Parse JSON payload fields:

  • FEATURE_DIR
  • FEATURE_SPEC
  • (Optionally capture IMPL_PLAN, TASKS for downstream use.)

If JSON parsing fails, abort and instruct the user to run /speckit.specify or verify the feature branch environment.

For single quotes in args like "I'm Groot", use escape syntax: e.g 'I'''m Groot' (or double-quote if possible: "I'm Groot").

2. Check for Existing Pending Iteration

Check if FEATURE_DIR/pending-iteration.md already exists. If it does:

  • Warn the user: "A pending iteration already exists. Running define again will overwrite it."
  • Show the existing file's change_request and created date from its frontmatter.
  • Ask the user to confirm before proceeding, or suggest running /speckit.iterate.apply first.

3. Load Current Artifacts

Read all available artifacts from FEATURE_DIR:

  • REQUIRED: spec.md — requirements, user stories, edge cases, scope
  • IF EXISTS: plan.md — tech stack, architecture, file structure, phases
  • IF EXISTS: tasks.md — task list with IDs, phases, checkboxes, dependencies
  • IF EXISTS: data-model.md — entities, attributes, relationships
  • IF EXISTS: research.md — technical decisions and constraints
  • IF EXISTS: quickstart.md — integration/test scenarios
  • IF EXISTS: checklists/ — quality checklists

Read the full file on GitHub · 260 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.

  1. 4d ago First seen · 260 lines · 28 tokens per session scan C 16576026b003

Subscribe to this mod's changes

define is a command 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 2,309 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (tells the agent never to refuse). It is 97% identical to speckit.iterate.define, differing in 16 lines, and is treated as a copy.