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.
npx skills add SteveVitali/agent-skills --skill reconcile-buildgit clone --depth 1 https://github.com/SteveVitali/agent-skillsWrote 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/skills/stevevitali/agent-skills/reconcile-build)<a href="https://agentmods.dev/skills/stevevitali/agent-skills/reconcile-build"><img src="https://agentmods.dev/badge/skills/stevevitali/agent-skills/reconcile-build/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/skills/stevevitali/agent-skills/reconcile-build"><img src="https://agentmods.dev/badge/skills/stevevitali/agent-skills/reconcile-build.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.00119 | $0.01170 |
| Opus 5 | $0.00060 | $0.00585 |
| Sonnet 5 | $0.00024 | $0.00234 |
| Haiku 4.5 | $0.00012 | $0.00117 |
Grade A, and why
reconcile-build 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reconcile Build
Hold the closeout procedures a multi-session build runs after its tickets land — so they live in one place
with their templates and checkers, and the tail REC.* tickets just say "invoke reconcile-build mode=…"
(the way the docs tickets say "invoke refresh-repo-docs"). Folding these into orchestrate-build would push
that SKILL past the line ceiling and mix sequencing with content; this skill is the content.
Precedent.
agent-docs/refresh-repo-docsown the docs procedures theDOC.*tickets invoke;reconcile-buildowns the reconciliation procedures theREC.*tickets invoke. It reads and writes the committed build memory defined inskills/build-memory/layout.md(it cites that file, does not restate it):DEFERRALS.md,docs/adr/, the ledger'sOPEN FINDINGS,COVERAGE_MATRIX.csv,BUILD_INDEX.md, and theBACKLOG.*/*_PLAN.md/OPERATIONAL_READINESS.mdoutputs underdocs/build/.
Orient
Resolve the memory root (build-memory memory-root.sh); confirm docs/build/ exists and the validator is
green (check-build-memory.sh .) before reconciling — reconciliation over an inconsistent layout is noise. Then
follow the mode.
The modes
| Mode | File | Produces |
|---|---|---|
backlog |
modes/backlog.md | docs/build/BACKLOG.csv, BACKLOG.md, OPERATIONAL_READINESS.md — every owed thing in exactly one row; readiness with a proof on every critical-path step. |
spec |
modes/spec.md | docs/build/TICKET_VS_SPEC.md, SPEC_RECONCILIATION_PLAN.md — what the build did vs what the spec said, and the amendments to fold back. |
integration |
modes/integration.md | docs/build/INTEGRATION_PLAN.md, a release-notes draft, and a planning/<date>_decision-memo.md seeding the next round. |
The one discipline that matters
Every owed thing lands in exactly one backlog row. The failure mode of build closeout is debt that is
"tracked" in five places and therefore nowhere. backlog gathers every source — each OPEN/PARTIAL deferral,
each ADR revisit trigger, each OPEN FINDINGS entry, each spec-mandated register's deferred row, each non-MET
coverage-matrix row — into a single sources cell, and scripts/check-backlog.sh fails if any source appears
zero times or more than once. That is the backlog's contract: complete and non-duplicating.
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 68 lines · 119 tokens per session scan A fc6bd70ec6f6
reconcile-build is a skill published in the GitHub repository SteveVitali/agent-skills (12 stars, last pushed yesterday), licensed MIT. It adds 119 tokens to every session and 1,170 once invoked, about $0.0006 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-09-10.
Other skills, from other repositories
neat-freak
Knowledge and governance closeout: reconcile project docs, rule files (CLAUDE.md/AGENTS.md), authorized agent memory, and workspace residue with what the code and runtime actually do, so the next session or the next person starts from one current answer. Trigger when the user names "neat-freak", "洁癖", or "/neat" — and…
state
Use when the user says 'update state', 'project state', 'where was I', or at session start to load current context.
handoff
Use when work is changing sessions, agents, or machines and the next pass needs a compact handoff document with current state, open questions, and next steps instead of raw chat history.
mastermind-project-history
Retrieve and reason from durable project decisions, failed approaches, audits, reports, and lessons without treating provenance, search rank, or user approval as technical proof. Use when asking why a design exists, whether an approach was tried, what supersedes an older decision, what prior evidence should constrain…
project-context
Resume, handoff, and long-running repo work by keeping durable context across threads or agents: task briefs, logs, and reusable reference notes.
continue
Use when you need the Codex Copilot equivalent of Claude Copilot /continue: resume paused or previous work from tc tasks, work products, memory, and stream context.