Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add naimkatiman/continuous-improvement/plugin install 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/skills/naimkatiman/continuous-improvement/reconcile)<a href="https://agentmods.dev/skills/naimkatiman/continuous-improvement/reconcile"><img src="https://agentmods.dev/badge/skills/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.1 | $0.00000 | $0.03329 |
| Opus 5 | $0.00000 | $0.01665 |
| Sonnet 5 | $0.00000 | $0.00666 |
| Haiku 4.5 | $0.00000 | $0.00333 |
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 yesterday.
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 — 182 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
Law 1 says research before executing. The most expensive skipped research is the state of your own repo: a branch that shifted under you, a push that silently did not land, a stash from a session you forgot. This skill establishes git ground truth first, acts only on a known state, stops at every operation that is hard to reverse, and then carries that known-good state all the way through a single-concern commit, a push, and an open PR — ending back on an up-to-date default branch once the PR merges.
When to Activate
- Before any branch/merge/rebase/push when more than one session, loop, or agent may be writing to the tree.
- When the working tree looks different from what you expect (unexpected branch, surprise modifications, a half-finished merge).
- Before cleaning up: consolidating branches, dropping stashes, removing worktrees.
- When finished work needs to land: stage it, commit one concern, push a feature branch, open a PR, and return to an up-to-date default branch.
- After a push, to confirm it actually landed on the remote.
Establish Ground Truth First
Read before you write. One command runs the whole pass and prints the resolved-state block:
npx ci-reconcile # resolved-state block; exit 1 if anything blocks a mutation
npx ci-reconcile --json # the same state, machine-readable
npx ci-reconcile --explain # print the probe set and why each probe runs
Exit codes: 0 nothing blocks, 1 at least one blocker, 2 not a git repository. The probe set is defined once in src/lib/git-state.mts, and npm run verify:reconcile-parity fails if this document drifts from it — the list below is the list the runner executes.
Run the pass by hand when the runner is not installed:
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 name; 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 for existence
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.
- yesterday Changed · -1 lines e58d37ba1508
- 8d ago First seen · 183 lines · 0 tokens per session scan A e1ef4604d27f
reconcile is a skill published in the GitHub repository naimkatiman/continuous-improvement (7 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,329 tokens. 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 skills, from other repositories
contextual-commit
Write contextual commits that capture intent, decisions, and constraints alongside code changes. Use when committing code, finishing a task, or when the user asks to commit. Extends Conventional Commits with structured action lines in the commit body that preserve WHY code was written, not just WHAT changed.
meta-pre-commit-quality-gate
Run three quality gates (ruff + mypy + pytest) in parallel over the staged diff, then arbitrate a single BLOCK/APPROVE verdict. Use before committing changes locally when you want a comprehensive pre-commit gate beyond per-file linting — exactly the same gate set CI enforces.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
map-diff
Analyze the impact of staged git changes against the committed Cortex function knowledge graph — shows which downstream functions are affected before you commit.
caveman-commit
Write a Conventional Commits message compressed to intent only. Use for "write a commit", "commit message", /commit or /caveman-commit.
flag-cleanup
Weekly reusable-session feature-flag cleanup for {{targetrepo}}. Inventories every feature flag, classifies each as fully rolled out, long dead, partial rollout, or active experiment, removes the flag and the dead branch it guards on an isolated branch when the suite is green, and opens a PR — never touching a flag…