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 agentmods add commands/naimkatiman/continuous-improvement/reconcilegit clone --depth 1 https://github.com/naimkatiman/continuous-improvementWrote 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/naimkatiman/continuous-improvement/reconcile)<a href="https://agentmods.dev/commands/naimkatiman/continuous-improvement/reconcile"><img src="https://agentmods.dev/badge/commands/naimkatiman/continuous-improvement/reconcile.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 | $0.00080 | $0.01597 |
| Opus 5 | $0.00040 | $0.00798 |
| Sonnet 5 | $0.00016 | $0.00319 |
| Haiku 4.5 | $0.00008 | $0.00160 |
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 5d 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/reconcile — Ground Truth, Then Commit, Push, and Open the PR
Read the repo's real state before acting on it: a branch that shifted, a push that did not land, or another session mid-merge will burn a whole session if you assume instead of check. Once the state is known, /reconcile carries the work through to an open PR and back to an up-to-date default branch.
What it does
Snapshots the full git state in one pass, detects a concurrent writer, classifies the upstream relationship, then acts only on the known state — stopping at every operation that is hard to reverse. When work is ready, it stages by filename, commits one concern, pushes a feature branch, verifies the push landed, and opens a PR. After a human merges, it fast-forwards the default branch and checks it out. Backed by the reconcile skill.
Establish ground truth
One command, cross-platform, no shell required:
npx ci-reconcile # resolved-state block; exit 0 clear / 1 blocked / 2 not a repo
npx ci-reconcile --json # machine-readable
npx ci-reconcile --explain # the probe set and why each probe runs
The same pass by hand. src/lib/git-state.mts is the source of truth for this list, and npm run verify:reconcile-parity fails if this file drifts from it:
git rev-parse --show-toplevel # inside a work tree, and where
git rev-parse HEAD # the sha every later claim is relative to
git symbolic-ref --quiet --short HEAD # branch; NON-ZERO EXIT = detached HEAD
git rev-parse --abbrev-ref --symbolic-full-name @{u} # upstream, or non-zero = none configured
git rev-list --left-right --count @{u}...HEAD # behind/ahead — only after the line above succeeded
git status --porcelain=v1 # reported changes (inflated by autocrlf)
git diff --name-only --ignore-all-space # real content drift — the number to trust
git stash list
git worktree list --porcelain
git rev-parse --git-path MERGE_HEAD # in-progress op: test the RESOLVED path
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.
- 5d ago First seen · 102 lines · 80 tokens per session scan A c33eee9a04a6
reconcile is a command published in the GitHub repository naimkatiman/continuous-improvement (7 stars, last pushed 10d ago), licensed MIT. It adds 80 tokens to every session and 1,597 once invoked, about $0.0004 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
battlecard
Create a sales-ready competitive battlecard — positioning, feature comparison, objection handling, and win strategies.
release
Generate changelog, bump version, and create git tag.
review
Cold re-quiz on code that already shipped — your own session commits, not the change in front of you.
analyze-and-create-issue
Analyze codebase and create GitHub/GitLab/Forgejo issues per finding.
generate-report
Generate a professional HTML report from assessment results in the conversation.
data-flow-analysis
Trace how data flows through the system from input to output.