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-archive/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-archive)<a href="https://agentmods.dev/skills/cairn-framework/cairn/cairn-archive"><img src="https://agentmods.dev/badge/skills/cairn-framework/cairn/cairn-archive.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.00028 | $0.00485 |
| Opus 5 | $0.00014 | $0.00243 |
| Sonnet 5 | $0.00006 | $0.00097 |
| Haiku 4.5 | $0.00003 | $0.00049 |
Grade A, and why
cairn-archive 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 6d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- cairn-archive — 100% identical, 0 lines differ
What it actually says
Archive a completed change: move it to the dated archive.
Prerequisites
- All tasks in tasks.md are marked complete
cairn change accept <change-id>has passed- The project's own quality gates pass (the repository's instructions, its
gates:config, or its ordinary build and test commands for its language)
Steps
-
Identify the change to archive
If not specified, list active changes:
ls meta/changes/ -
Verify completion: every task in
meta/changes/<change-id>/tasks.mdis checked. When one is not, stop and report: a change with pending tasks stays active. -
Run final verification
Re-run the project's own gates so the archive lands on a clean tree. Use the same commands the repository documents for itself, in its own language.
-
Archive the change
Run the archive command. It validates the change against the current graph, applies the blueprint delta, refreshes generated output, logs the archival, and moves the change into the dated archive directory:
cairn change archive <change-id> -
Update any references: check
cairn.blueprint(changes blocks), README.md, and other documentation; update or remove stale references. -
Commit the archive
Read the touched paths from
git status --shortfirst, then stage exactly those (nevergit add -Aorgit add ., which would sweep in unrelated untracked files):git add <each path the archive touched> git commit -m "archive(change): move <change-id> to archive"
Guardrails
- Preserve the change directory structure in the archive (proposal.md, design.md, tasks.md, specs/).
- The archive is permanent history: never edit archived changes.
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.
- 6d ago First seen · 66 lines · 28 tokens per session scan A bcdff04bab3c
cairn-archive is a skill published in the GitHub repository cairn-framework/cairn (41 stars, last pushed yesterday), licensed Apache-2.0. It adds 28 tokens to every session and 485 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 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.