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 skills/cheswickdev/cairn/cairn-handoffnpx skills add CheswickDEV/cairn --skill cairn-handoffgit clone --depth 1 https://github.com/CheswickDEV/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/cheswickdev/cairn/cairn-handoff)<a href="https://agentmods.dev/skills/cheswickdev/cairn/cairn-handoff"><img src="https://agentmods.dev/badge/skills/cheswickdev/cairn/cairn-handoff.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.00086 | $0.00501 |
| Opus 5 | $0.00043 | $0.00251 |
| Sonnet 5 | $0.00017 | $0.00100 |
| Haiku 4.5 | $0.00009 | $0.00050 |
Grade A, and why
Cairn Handoff 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 3d 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.
What it actually says
Cairn Handoff — persist this session as a 7-bucket brief
Trigger: the user says "Cairn Handoff", or you are about to clear/finish the session or switch model/host.
Do this:
- Write a faithful 7-bucket brief from THIS conversation — nothing invented, nothing padded:
- DECISIONS (mark superseded ones), EVIDENCE (each with a source ref:
file:line,msg#, url, or tool output), OPEN QUESTIONS, CONSTRAINTS, VERBATIM (code/IDs/values/paths byte-exact), NEXT STEPS, DISCARDED.
- DECISIONS (mark superseded ones), EVIDENCE (each with a source ref:
- Call the
handoffMCP tool (leavemodeat its defaultaccount→ no model call, no egress; on Codex you write the brief on the user's ChatGPT/Codex subscription):brief: the full brief text.requiredVerbatim: every value that MUST survive byte-exact (IDs, exact numbers, file paths, flags).decisions/evidence: the structured form when you can extract it.host: the current model/provider;sourceZone: the current zone (green/yellow/red).
- Report back:
storedDecisionId,decisionsStored, andmissingRequired. IfmissingRequiredis non-empty, fix the brief so those spans appear byte-exact and callhandoffagain.
Notes:
- A new handoff supersedes the previous brief automatically, so the ledger stays lean — old briefs
do not pile up in
decision_log view=current. - Account mode persists locally only; nothing is sent to any model.
- To pick the work back up later, use "Cairn resume" (skill
cairn-resume).
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.
- 3d ago First seen · 30 lines · 86 tokens per session scan A dc1fa76b1fba
Cairn Handoff is a skill published in the GitHub repository CheswickDEV/cairn (1 stars, last pushed 2mo ago), licensed MIT. It adds 86 tokens to every session and 501 once invoked, about $0.0004 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-31.
Other skills, from other repositories
mnemo-cortex
Installs and wires Mnemo Cortex (local-first persistent memory) into OpenClaw and other MCP-capable agents. Use for cross-session recall, decision history, or multi-agent shared memory.
vibebox
Use this skill when an AI coding task should consult VibeBox memory before work as an auto-intervention memory layer for meaningful repository work; retrieve active guidance when available, apply it as context, and capture meaningful outcomes with userRequest plus AI-agent structured memory candidates unless the user…
coss-particles
Index of all COSS UI particle examples. Use when implementing UI features to find copy-paste-ready component patterns built on coss primitives. Each particle has a description and a JSON URL for easy installation.
skill-creator
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
lark-cli
Lark/Feishu CLI skills for Stella sessions. Covers workspace operations — calendar, docs, tasks, mail, and messenger — via the Stella-managed lark-cli tool. Stella installs the binary and injects a managed per-user OAuth token; no native CLI bootstrap is required. Always read lark-shared first for identity selection…
stella
Self-knowledge about stella, the self-hosted AI assistant. Use when the user asks about stella itself: configuration, setup, onboarding, providers, models, agents, channels (Telegram/Discord/QQ/Feishu/DingTalk/WeChat), webhooks, memory system (LCM), scheduled jobs, reusable workflows, goals (objectives that converge…