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.
git clone --depth 1 https://github.com/terrene-foundation/kailash-coc-claude-pyWrote 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/terrene-foundation/kailash-coc-claude-py/reconcile-notes)<a href="https://agentmods.dev/commands/terrene-foundation/kailash-coc-claude-py/reconcile-notes"><img src="https://agentmods.dev/badge/commands/terrene-foundation/kailash-coc-claude-py/reconcile-notes/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/commands/terrene-foundation/kailash-coc-claude-py/reconcile-notes"><img src="https://agentmods.dev/badge/commands/terrene-foundation/kailash-coc-claude-py/reconcile-notes.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.00056 | $0.01894 |
| Opus 5 | $0.00028 | $0.00947 |
| Sonnet 5 | $0.00011 | $0.00379 |
| Haiku 4.5 | $0.00006 | $0.00189 |
Grade A, and why
reconcile-notes scanned grade A with 1 finding 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 8d 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
const { execFileSync } = require("child_process"); How it starts
The opening of the file, as written. The whole thing — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
What /reconcile-notes Is
/reconcile-notes brings YOUR OWN session-notes fragment back into coherence after you
incorporate sibling work (a git merge/pull/rebase, or a checkout main). It prunes
items the incorporated work has ALREADY LANDED, re-points stale read-first pointers, and
stamps the incorporation-guard's lag anchor (last_reconciled_sha) to HEAD so the advisory
stops firing until the notes drift again.
It is the RECONCILE half of the #743 coherence layer; the DETECTION half
(session-notes-incorporation-guard.js, Wave 2) is what tells you the notes lag and points
you here. This command NEVER edits another operator's fragment, NEVER edits the shared forest
ledger except through the layout writer, and NEVER re-derives content from anything but the
fragment + git state (memory-only).
Scope Fence (BLOCKED outside it)
- Own fragment only (C4.1): writes ONLY
.session-notes.d/<your display_id>.md. Editing a sibling's fragment is BLOCKED (each fragment is single-writer perknowledge-convergence.mdMUST-1). - Memory-only (C4.2): reason over the fragment's content +
git log/git rev-list. NO external re-derivation, NO changelog scrape, NO reading other repos. - Prune only with a CITED DURABLE receipt (C4.4 + I9, Decision-1): an item may be pruned ONLY when a durable receipt proves it landed — a commit SHA, a merged-PR number, or a journal slot. "Looks done" / "probably landed" is BLOCKED. Prune targets: landed in-flight items, fixed traps, moved read-first pointers, merged-closed ledger rows.
Workflow
0. Resolve identity + locate your fragment
Resolve your own fragment path — never a hand-slugified filename:
node -e 'const{resolveIdentity}=require("./.claude/hooks/lib/operator-id.js");const{fragmentPathFor}=require("./.claude/hooks/lib/session-notes-layout.js");const id=resolveIdentity(process.cwd(),{});console.log(fragmentPathFor(process.cwd(),id))'
If the fragment does not exist yet (never migrated / never reconciled), there is nothing to
reconcile — STOP and report. Read the fragment; note its current last_reconciled_sha (the
lag anchor set by the last reconcile or by migration).
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.
- 8d ago First seen · 139 lines · 56 tokens per session scan A 448f23beab29
reconcile-notes is a command published in the GitHub repository terrene-foundation/kailash-coc-claude-py (12 stars, last pushed 24d ago), licensed Apache-2.0. It adds 56 tokens to every session and 1,894 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other commands, from other repositories
context
A project-context command that manages a .context directory containing decision notes, session logs, and history. It helps keep a record of why changes were made across Git branches and commits.
bm
Ask basemind anything about the current codebase — outlines, refs, callers, git history, blame, diffs, docs, memory.
context-load
Carga de contexto al inicio de sesión. Lee estado del workspace, decisiones recientes, último session save y actividad Git para arrancar con el big picture.
cache-invalidate
Invalidación selectiva de capas de caché con rollback seguro.
review-code
Read ALL memory bank code rules + best practices, check the files that changed, and APPLY fixes so they adhere. The active counterpart to /scan (which is read-only). Use after an AI session, before commit, to make changed files compliant.
vouch-propose-from-pr
Distill a merged PR into vouch claim proposals.