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/sdotj/sleeper-bot/cairn-archivenpx skills add sdotj/sleeper-bot --skill cairn-archivegit clone --depth 1 https://github.com/sdotj/sleeper-botWrote 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/sdotj/sleeper-bot/cairn-archive)<a href="https://agentmods.dev/skills/sdotj/sleeper-bot/cairn-archive"><img src="https://agentmods.dev/badge/skills/sdotj/sleeper-bot/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 5d 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.
This is a copy
100% identical to cairn-archive — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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.
- 5d ago First seen · 66 lines · 28 tokens per session scan A bcdff04bab3c
cairn-archive is a skill published in the GitHub repository sdotj/sleeper-bot (0 stars, last pushed yesterday), licensed MIT. 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. It is 100% identical to cairn-archive, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…