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.apply)<a href="https://agentmods.dev/commands/opsmill/infrahub-mcp/speckit.iterate.apply"><img src="https://agentmods.dev/badge/commands/opsmill/infrahub-mcp/speckit.iterate.apply.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.00026 | $0.02237 |
| Opus 5 | $0.00013 | $0.01118 |
| Sonnet 5 | $0.00005 | $0.00447 |
| Haiku 4.5 | $0.00003 | $0.00224 |
Grade A, and why
speckit.iterate.apply 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 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.
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
1 near-identical copy found in the catalogue:
- apply — 97% identical, 23 lines differ
How it starts
The opening of the file, as written. The whole thing — 231 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).
If the user provides arguments, treat them as adjustments or notes for the apply process (e.g., "skip task completion marking" or "only update spec.md and tasks.md"). The primary source of truth for what to change is pending-iteration.md.
Outline
Goal: Execute the iteration plan defined in pending-iteration.md by updating all spec artifacts that speckit.implement relies on. After apply completes, the user can go directly to /speckit.implement — skipping /speckit.plan and /speckit.tasks since this command already handles those updates.
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. Load Pending Iteration
Check for FEATURE_DIR/pending-iteration.md. If it does not exist, abort with:
No pending iteration found. Run
/speckit.iterate.define <change request>first to define what you want to change.
If it exists, read and parse the file:
- Frontmatter:
status,created,change_request,scope - Change Summary: What this iteration does
- Implementation Progress: Current state context
- Impact Assessment: Which artifacts need updates and how
- Risk Checks: Acknowledged risks
- Planned Changes: Specific changes per artifact
If status is not pending, warn the user that this iteration may have already been applied.
3. Load Current Artifacts
Read all available artifacts from FEATURE_DIR:
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 · 231 lines · 26 tokens per session scan A b9995f02ee05
speckit.iterate.apply is a command published in the GitHub repository opsmill/infrahub-mcp (10 stars, last pushed yesterday), licensed Apache-2.0. It adds 26 tokens to every session and 2,237 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.