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-explorenpx skills add sdotj/sleeper-bot --skill cairn-exploregit 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-explore)<a href="https://agentmods.dev/skills/sdotj/sleeper-bot/cairn-explore"><img src="https://agentmods.dev/badge/skills/sdotj/sleeper-bot/cairn-explore.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.00000 | $0.00741 |
| Opus 5 | $0.00000 | $0.00370 |
| Sonnet 5 | $0.00000 | $0.00148 |
| Haiku 4.5 | $0.00000 | $0.00074 |
Grade A, and why
cairn-explore 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 2d 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-explore — 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
Explore the Cairn architecture graph.
Commands
cairn status- project summary (nodes, edges, findings)cairn get <node>- detailed info for a nodecairn neighbourhood <node>- dependencies and dependentscairn files <node>- files owned by a nodecairn islands- disconnected componentscairn lint- findings across the project (--node <id>scopes to one node); exits 1 when an Error finding is presentcairn ui- visual graph explorer in a browsercairn rationale <node>- accepted decisions and provenance chain behind a node (why it exists)cairn decisions <node>- decision artefacts attached to a nodecairn research <node>- research artefacts linked to a nodecairn sources <node>- external sources a node citescairn change list --json- registered change proposals (the--jsonflag is required)
Steps
- Pick the target: ask when the request names none:
"What would you like to explore? A specific node, the overall health, or something else?"
- Run the matching command(s) and show the output.
- Interpret the results in plain English:
synced- node matches the filesystemghost- declared in blueprint but missing on diskorphaned- exists on disk but not declareddrift- declared but contradicts observed state- Findings severity: Error > Warning > Info
- Suggest the next step:
cairn scanto refresh the graph,cairn lintfor detailed findings, a blueprint edit for structural issues, orcairn refineto generate a change proposal from code changes.
Provenance: why a node is shaped the way it is
For "what decisions affect node X" or "why was X built this way", query
cairn rationale <node> first: it returns the node's accepted decisions with
their provenance links (informed_by, related, refines, supersedes), so
there is no need to grep meta/decisions/ by hand. cairn decisions <node>
adds decisions in other states (proposed, deprecated, superseded); --json
gives the structured fields. The reconciled graph is the authority: when an
auto-generated guidance block contradicts an accepted decision, the decision
cairn returns wins.
Where cairn cannot help: read the source
The graph models blueprint structure plus artefacts (decisions, research, contracts, todos), not source symbols. For enum variants, struct fields, function definitions, or call sites, read the source files directly rather than expecting a cairn query to answer.
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.
- 2d ago First seen · 61 lines · 0 tokens per session scan A 51bb72a57d4f
cairn-explore is a skill published in the GitHub repository sdotj/sleeper-bot (0 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 741 tokens. A static security scan graded it A with 0 findings. It is 100% identical to cairn-explore, 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…