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 uHappyLogic/cairn --skill goto-next-milestonegit clone --depth 1 https://github.com/uHappyLogic/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/uhappylogic/cairn/goto-next-milestone)<a href="https://agentmods.dev/skills/uhappylogic/cairn/goto-next-milestone"><img src="https://agentmods.dev/badge/skills/uhappylogic/cairn/goto-next-milestone/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/uhappylogic/cairn/goto-next-milestone"><img src="https://agentmods.dev/badge/skills/uhappylogic/cairn/goto-next-milestone.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.00024 | $0.00726 |
| Opus 5 | $0.00012 | $0.00363 |
| Sonnet 5 | $0.00005 | $0.00145 |
| Haiku 4.5 | $0.00002 | $0.00073 |
Grade A, and why
goto-next-milestone 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 4d 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
goto-next-milestone
Activates an already-defined milestone by updating milestones/README.md to point to it as the current milestone. The milestone directory must already exist (created by /define-milestone-goal); this skill creates no files or directories. Run this after /finish-current-milestone has cleared the current pointer to "none".
Usage
/goto-next-milestone
No arguments. The milestone to activate is discovered automatically.
Workflow
1. Check prerequisites
Read milestones/README.md and find the line whose prefix is Current milestone:. If that line is not Current milestone: none (i.e. it still points to an active milestone path), stop and tell the user to run /finish-current-milestone first.
2. Find the candidate milestone
Read milestones/README.md and scan milestones/ to collect:
- All directories matching
milestone_<N>_<slug>/ - All milestone dirs already listed in the
## Milestone Historysection (these are completed)
The candidates are directories that exist in milestones/ but do not appear in ## Milestone History.
- Zero candidates: stop. Tell the user to run
/define-milestone-goalfirst to create a milestone. - One candidate: confirm the path and title with the user, then proceed.
- Multiple candidates: list them (number, slug, path) and ask the user which one to activate before proceeding. When deriving the number from the directory slug, strip leading zeros and treat it as an integer (e.g.
milestone_01_foo→ number1).
3. Update milestones/README.md
In milestones/README.md, overwrite the Current milestone: line with:
Current milestone: `milestones/milestone_<number>_<slug>/`
Leave the ## Current Milestone heading, the ## Milestone History section, and all other content unchanged; update milestones/README.md only — never write the pointer into CLAUDE.md.
4. Commit the activation
Read and follow the shared commit procedure at .agents/plugins/cairn/shared/commit-procedure.md, carrying out its steps yourself. Supply it these two inputs:
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.
- 4d ago Changed 4d2e77d91098
- 6d ago Changed · -6 lines · -34 tokens per session 1b8bfba0e615
- 11d ago First seen · 72 lines · 58 tokens per session scan A a20ffe6a26ab
goto-next-milestone is a skill published in the GitHub repository uHappyLogic/cairn (2 stars, last pushed yesterday), licensed MIT. It adds 24 tokens to every session and 726 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-31.
Other skills, from other repositories
debt-ops-add
Register a deferred decision in the tech-debt registry. Trigger by judgment, not a marker scan, whenever a future reader would ask "why this way?": an unmade decision, stub, loosened type, bypassed check, swallowed error, a default picked "for now", or a TODO/FIXME/HACK/XXX marker. Trigger immediately whenever you…
plan-task
Structured task planning using Work files. Use for any new feature, bug fix, or project that needs a task breakdown before implementation.
dont-leave-me
A stop-before-finishing checklist for an agent that checks whether requested work, changed files, verification, and cleanup have actually been handled.
log
Capture front door. Logs 1..N observations as card files at docs/work/{ID}.md (BUG / DEBT / GAP), gateway-inline — no dispatch. Use when the user says "log this", "track that", "note this down", or types /super-bootstrap:log — and when Claude needs to file its own findings (out-of-scope findings from a review, audit…
triage
Read-only grounding phase for a card — every card''s pickup. /super-bootstrap:triage {ID} dispatches the triage subagent (inherit — the session owner's model) to ground the card cold — premise verify, aim validate, blast collect — and append a Verdict block — ## Verdict — auto-fix · {date} (Fix-shape / Probe-deps /…
drain
Parallel-worktree auto-drain of the board. One /super-bootstrap:drain turn = scan the pipeline sources (specs/plans/backlog, plus the scale module's test queue when present) → keep only admissible items → relation-analyze into a conflict-free wave → confirm with the user → spawn one isolated git worktree + headless…