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.reconcile.run)<a href="https://agentmods.dev/commands/opsmill/infrahub-mcp/speckit.reconcile.run"><img src="https://agentmods.dev/badge/commands/opsmill/infrahub-mcp/speckit.reconcile.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.
<a href="https://agentmods.dev/commands/opsmill/infrahub-mcp/speckit.reconcile.run"><img src="https://agentmods.dev/badge/commands/opsmill/infrahub-mcp/speckit.reconcile.run.svg" alt="Reviewed on agentmods" width="80" 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.00016 | $0.01939 |
| Opus 5 | $0.00008 | $0.00970 |
| Sonnet 5 | $0.00003 | $0.00388 |
| Haiku 4.5 | $0.00002 | $0.00194 |
Grade A, and why
speckit.reconcile.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 9d 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:
- reconcile — 92% identical, 14 lines differ
How it starts
The opening of the file, as written. The whole thing — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Act as the Chief Software Architect and Implementation Auditor. A feature implementation has landed, but "artifact drift" has been discovered (e.g., missing routes, updated behavior, or unlinked UI). Your goal is to reconcile this drift by surgically amending the feature's own specification, plan, and task artifacts.
User Input
$ARGUMENTS
Input Parsing
The input $ARGUMENTS is a Gap Report — a natural language description of what is missing or changed in the implementation versus the documentation.
Examples:
- "Backend + tests for Invoice Settings exist; React screen scaffolded. Users can't navigate to it. Need sidebar link + route."
- "The /api/v1/settings endpoint now requires an 'org_id' header not in the original plan."
If $ARGUMENTS contains any of these flags, respect them (optional):
--spec-only— update onlyspec.md--plan-only— update onlyplan.md--tasks-only— update onlytasks.md
If $ARGUMENTS is empty, output ERROR: No gap report provided. Usage: /speckit.reconcile.run [gap report text] and stop.
Step 0: Discovery & Setup (Gate)
0.1 Resolve Paths
Run .specify/scripts/bash/check-prerequisites.sh --json --paths-only --include-tasks to identify the active feature directory and its artifacts. This script is mandatory for path discovery. If the script is missing, stop and inform the user.
Derive absolute paths for:
FEATURE_DIR(e.g.,specs/###-feature-name/)FEATURE_SPEC(FEATURE_DIR/spec.md)IMPL_PLAN(FEATURE_DIR/plan.md)TASKS_FILE(FEATURE_DIR/tasks.md)
Validation: Ensure spec.md and plan.md exist. If either is missing, stop with:
⚠️ Missing required files in
FEATURE_DIR. Expected: spec.md, plan.md. Run/speckit.specifyand/speckit.planfirst.
If tasks.md does not exist, create it with a ## Remediation: Gaps heading before appending tasks.
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.
- 9d ago First seen · 194 lines · 16 tokens per session scan A d886dda7042b
speckit.reconcile.run is a command published in the GitHub repository opsmill/infrahub-mcp (10 stars, last pushed 2d ago), licensed Apache-2.0. It adds 16 tokens to every session and 1,939 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.