Borrowing it
Nothing to install: this file belongs to cairn-framework/cairn. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/cairn-framework/cairn/main/.claude/skills/cairn-loop-reconcile/SKILL.mdgit clone --depth 1 https://github.com/cairn-framework/cairnWrote 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/cairn-framework/cairn/cairn-loop-reconcile)<a href="https://agentmods.dev/skills/cairn-framework/cairn/cairn-loop-reconcile"><img src="https://agentmods.dev/badge/skills/cairn-framework/cairn/cairn-loop-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.00067 | $0.01446 |
| Opus 5 | $0.00034 | $0.00723 |
| Sonnet 5 | $0.00013 | $0.00289 |
| Haiku 4.5 | $0.00007 | $0.00145 |
Grade A, and why
cairn-loop-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 7d 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reconcile the remaining plan
Loaded by cairn-dev loop mode after Verify and before Land. Inputs: the
selected unit (slug or finding code), its resolved node, its validated todo
body when it has one, the proof Verify produced, and the bound $CAIRN.
A campaign runs across many fresh sessions with no memory between them. The plan the next session reads is whatever this commit leaves on main. Much of the work is research based, so a landed unit routinely invalidates a later one. Recording that is part of the unit, not paperwork after it.
Declared exits, exactly one, as the last line you return to loop mode:
RECONCILED: the plan on disk matches this unit's evidence, and the edits sit in the worktree for Land to stage.LOOP HALTED: reconciling needs a maintainer ruling this session cannot make.
Provenance only. This recipe never selects the next unit, never repeats, never
retries, never interprets a terminal token, and never commits or pushes. Land
owns the commit; the invoking user or harness owns repetition
(dec.no-orchestrator, dec.loop-command-harness-model).
Authoring paths
Every obligation below has one path. $CAIRN research, $CAIRN todos, and
$CAIRN decisions are read-only queries, not creation verbs.
| Obligation | Path |
|---|---|
| Observation and result | hand-author meta/research/<slug>.md (id res.<slug>, nodes: required) |
| A rule changed | $CAIRN decision new <slug> --node <id>, then author the body |
| Status change | $CAIRN todo set <slug> <open|in_progress|done|blocked> |
| New prerequisite | $CAIRN todo new <slug> --node <id> |
| Todo body, Depends on, umbrella Waves, change spec | direct file edit |
1. Record the observation
If this unit produced evidence (a measurement, a rejected option, a behaviour the plan did not predict), write it as a Research artefact naming the node it constrains. If it changed a rule rather than only informing one, write a Decision as well and state retain, revise, or remove for the hypothesis the unit tested.
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.
- 7d ago First seen · 124 lines · 67 tokens per session scan A e597a037db7f
cairn-loop-reconcile is a skill published in the GitHub repository cairn-framework/cairn (41 stars, last pushed yesterday), licensed Apache-2.0. It adds 67 tokens to every session and 1,446 once invoked, about $0.0003 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 skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.