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/speckit.iterate.define)<a href="https://agentmods.dev/commands/opsmill/infrahub-mcp/speckit.iterate.define"><img src="https://agentmods.dev/badge/commands/opsmill/infrahub-mcp/speckit.iterate.define.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.00028 | $0.02328 |
| Opus 5 | $0.00014 | $0.01164 |
| Sonnet 5 | $0.00006 | $0.00466 |
| Haiku 4.5 | $0.00003 | $0.00233 |
Grade C, and why
speckit.iterate.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 8d 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. Copies of this mod
1 near-identical copy found in the catalogue:
- define — 97% identical, 16 lines differ
How it starts
The opening of the file, as written. The whole thing — 264 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_DIRFEATURE_SPEC- (Optionally capture
IMPL_PLAN,TASKSfor 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_requestandcreateddate from its frontmatter. - Ask the user to confirm before proceeding, or suggest running
/speckit.iterate.applyfirst.
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
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.
- 8d ago First seen · 264 lines · 28 tokens per session scan C 980309226fbb
speckit.iterate.define is a command published in the GitHub repository opsmill/infrahub-mcp (10 stars, last pushed 3d ago), licensed Apache-2.0. It adds 28 tokens to every session and 2,328 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). 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.