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/conorbronsdon/agent-context-os/reconcilegit clone --depth 1 https://github.com/conorbronsdon/agent-context-osWrote 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/conorbronsdon/agent-context-os/reconcile)<a href="https://agentmods.dev/commands/conorbronsdon/agent-context-os/reconcile"><img src="https://agentmods.dev/badge/commands/conorbronsdon/agent-context-os/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.00017 | $0.01659 |
| Opus 5 | $0.00009 | $0.00830 |
| Sonnet 5 | $0.00003 | $0.00332 |
| Haiku 4.5 | $0.00002 | $0.00166 |
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 today.
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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/reconcile — Multi-Session Drift Check
When multiple agent sessions run in parallel (especially with worktrees), files drift out of sync. This core scans for inconsistencies and proposes fixes — it flags problems but doesn't fix them without approval.
This is the generic core. A consuming repo with single-source-of-truth rules (e.g. a pipeline file that other files reference) adds those specific cross-checks as its own overlay — see step 4.
Invocation: this command is user-only because its optional fix mode can write and commit. The default scan remains read-only. It never pulls, rebases, or moves the working tree — sync divergence is reported, not fixed. A home that wants a sync-first reconcile adds a pull step in its own overlay, and should weigh the cost first: an auto-rebase in a shared checkout can strand other sessions' worktree bases, which is the exact situation this core is run to diagnose. Everything that changes files is proposed and separately approved before it is applied.
Configuration
Run bash scripts/contextos.sh workspace show and use its resolved state_dir
and task_file. Canonical JSON is authoritative; legacy YAML is used only when
JSON is absent. Stop and report a configuration error instead of guessing paths.
When to Use
- After merging worktree branches back to the default branch
- When something "feels off" after parallel work
- After a crash where multiple sessions were open
- As a periodic sanity check during heavy parallel workflows
Instructions
0. Orientation (run FIRST)
Scope the check and resolve the default branch before reading any files. Don't assume main:
git rev-parse --git-dir >/dev/null 2>&1 || { echo "not a git repository — nothing to reconcile"; exit 0; }
REPO_ROOT=$(git rev-parse --show-toplevel)
DEFAULT=$(git symbolic-ref --short refs/remotes/origin/HEAD 2>/dev/null | sed 's|^origin/||')
DEFAULT=${DEFAULT:-$(git remote show origin 2>/dev/null | sed -n 's/.*HEAD branch: //p')}
DEFAULT=${DEFAULT:-main} # no remote configured — fall back and say so in the report
find "$REPO_ROOT" -name "*.md" -mtime -1 -not -path "*/node_modules/*" | sort # recently modified
git -C "$REPO_ROOT" log --oneline -10
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.
- today Changed d04b5f2f1edb
- 5d ago First seen · 131 lines · 17 tokens per session scan A 63e49cffd608
reconcile is a command published in the GitHub repository conorbronsdon/agent-context-os (22 stars, last pushed today), licensed MIT. It adds 17 tokens to every session and 1,659 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-30.
Other commands, from other repositories
cm-connect
Hook this repo and another to the shared memory layer end to end — survey, operator-confirmed enrollment, an optional shared fact, absorption both ways, and the network payoff.
cm-doctor
Print the resolved StoreContext (native/canonical/control-plane paths, enrollment, registry health).
generate-docs
Generates a Rust-scoped symbol inventory to assist agents in understanding the public API surface of the workspace.
extensions
Show what the connected context expects to reach, and whether this machine provides it.
list
List the NeatContext contexts you can connect.
ctx
Experimental integration for ctx in Cursor.