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 skills add isaacriehm/cairn --skill cairn-resyncgit clone --depth 1 https://github.com/isaacriehm/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/isaacriehm/cairn/cairn-resync)<a href="https://agentmods.dev/skills/isaacriehm/cairn/cairn-resync"><img src="https://agentmods.dev/badge/skills/isaacriehm/cairn/cairn-resync/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/skills/isaacriehm/cairn/cairn-resync"><img src="https://agentmods.dev/badge/skills/isaacriehm/cairn/cairn-resync.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.00034 | $0.01519 |
| Opus 5.5 | $0.00014 | $0.00608 |
| Sonnet 5.5 | $0.00007 | $0.00304 |
| Haiku 4.5 | $0.00003 | $0.00152 |
Grade A, and why
cairn-resync 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 1mo 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: cairn-resync
Host portability
This skill is shared by Claude Code, Cursor, and Codex. Resolve Cairn MCP
tools with the host's native discovery mechanism and use its structured
question UI, falling back to a concise A/B/C chat question. Named curator
briefs live under ../../agents/; dispatch them natively after reading the
brief, or execute inline only when the host has no subagent capability.
You are running Cairn's operator-initiated re-discovery so committed ground state catches up to a tree that has grown or been restructured since adoption.
Everything here is opt-in, recoverable, and never auto-applies to
committed ground: deterministic edits are review-class (the operator
commits the diff); LLM passes spend the fast tier only on genuinely-new
prose; re-curation produces _inbox/ drafts the operator drains. Confirm
scope with the operator before any pass that spends model quota (re-cluster,
re-curate).
Pass 1 — config-resync (deterministic, free)
Resolve the config-drift the sensor surfaced.
- Preview:
cairn_resync({})(dry-run default). Summarize the proposed.cairn/config.yamledits — add a grown dir tocomponentDirs, add a new file type toextensions, add a.gitignoreentry tooff_limits, drop a deadcomponentDir, re-point a moved entity'ssource_file. - On the operator's OK:
cairn_resync({ apply: true }). It archives the pre-resyncconfig.yamlto.cairn/ground/.archive/and is idempotent. Tell the operator to review + commit the diff. - Pass
areato scope either call to one subtree.
Pass 2 — topic re-cluster (LLM, opt-in)
Offer this when prose has moved/grown enough that the topic-index is stale. Confirm first — it spends the fast tier (only on new prose; unchanged pairs hit the cache).
- Preview:
cairn_resync({ recluster: true })— re-walks + judges and reportstopics_before → topics_after+judge_calls_fresh, but overwrites no map. - On OK:
cairn_resync({ recluster: true, apply: true })— archives the priortopic-index.yaml+anchor-map.yaml, then rebuilds them. The maps are gitignored, per-clone derived state, so there's nothing to commit.
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.
- 1mo ago First seen · 122 lines · 34 tokens per session scan A feae287ee23a
cairn-resync is a skill published in the GitHub repository isaacriehm/cairn (6 stars, last pushed 19d ago), licensed MIT. It adds 34 tokens to every session and 1,519 once invoked, about $0.0001 per session on Opus 5.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 skills, from other repositories
ccs-align
Run the CCS Align seat's hourly breathing cycle — prove the local claude-mem worker is healthy, pull needle observations through search → timeline → getobservations, land them in a seat-owned middle cache via atomic grab → append → filter exclude-marks → replace, manage exclude marks, and walk house → project → seat…
weekly-digests
Generate a serial week-by-week narrative digest of a project's full claude-mem timeline. Splits the timeline into per-ISO-week files, then runs one consecutive subagent per week — each receiving the prior week's carry-forward block — to produce one chapter per ISO week of data. Use when asked for "weekly digests"…
mode-creator
Interactively create, install, activate, and verify custom claude-mem modes, including domain-specific observation types, concept tags, optional Telegram alerts, bot setup, worker restart, and startup-context verification. Use this whenever someone asks to customize what claude-mem remembers, create or change a mode…
handoff
Generate a HANDOFF.md that captures goal, current state, files touched, failed attempts, and next steps — so a fresh Claude session can continue exactly where this one left off. Use when sessions are getting long, Claude keeps retrying the same broken solution, or the user wants to step away and resume later.
cloud-sync
Set up or check claude-mem cloud sync with cmem.ai Pro. Use when the user says "set up cloud sync", "sync my memories", "cmem pro", "cloud backup", "sync status", or wants their memory database backed up or synced to their cmem.ai account.
screenpipe
Search screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe.