A command that brings a feature’s specification, implementation plan, and task list back in line with what was actually built. It accepts a description of the differences and can limit which document types it updates.

Use it after implementation to record missing work, changed requirements, or behavior that the original feature documents do not describe.

It prevents project documentation from becoming misleading after routes, behavior, or other implementation details change.

reconcile — Command 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.

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

Your own site

<a href="https://agentmods.dev/commands/opsmill/infrahub-mcp/reconcile"><img src="https://agentmods.dev/badge/commands/opsmill/infrahub-mcp/reconcile/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/commands/opsmill/infrahub-mcp/reconcile"><img src="https://agentmods.dev/badge/commands/opsmill/infrahub-mcp/reconcile.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 16 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,901 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 92% 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.00016	$0.01901
Opus 5	$0.00008	$0.00950
Sonnet 5	$0.00003	$0.00380
Haiku 4.5	$0.00002	$0.00190

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

Security

Grade A, and why

reconcile 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 6d 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

92% identical to speckit.reconcile.run — 14 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/reconcile/commands/reconcile.md · 190 lines

How it starts

The opening of the file, as written. The whole thing — 190 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 only spec.md
--plan-only — update only plan.md
--tasks-only — update only tasks.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 {SCRIPT} 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.specify and /speckit.plan first.

If tasks.md does not exist, create it with a ## Remediation: Gaps heading before appending tasks.

0.2 Load Context

Read FEATURE_SPEC, IMPL_PLAN, and TASKS_FILE.

Also read .specify/memory/constitution.md if it exists. If found, extract MUST-level constraints and Architecture Standards. These are enforced in Step 1 — any remediation item that conflicts with a MUST principle is flagged as CRITICAL:

🔴 CONSTITUTION CONFLICT: [remediation item] conflicts with [principle]
→ This must be resolved in Step 2 clarification before edits proceed.

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

6d ago First seen · 190 lines · 16 tokens per session scan A 9438f365e4b8

Subscribe to this mod's changes

reconcile 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,901 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to speckit.reconcile.run, differing in 14 lines, and is treated as a copy.

LLM Planning Project management agent ai coding-agent infrahub infrastructure

hep-graph.body

A command for viewing saved Agentlas automation graphs and requesting that one be run. The desktop app performs the actual run.

agentlas-ai/Agentlas-OS · 0 tokens

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.

0xK3vin/MegaMemory · 0 tokens

pm-review-user-01-happy

Un PRD est disponible dans output/. Le wiki contient des pages persona- et interview- avec des verbatims. Le pm-user-advocate vérifie l'alignement du PRD avec les personas, identifie les personas non servis, cite les verbatims contradictoires, et évalue le niveau de confiance de chaque claim. Une page type…

evb87-tech/corpus · 0 tokens

reconcile