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 finish-current-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/finish-current-milestone)<a href="https://agentmods.dev/skills/uhappylogic/cairn/finish-current-milestone"><img src="https://agentmods.dev/badge/skills/uhappylogic/cairn/finish-current-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/finish-current-milestone"><img src="https://agentmods.dev/badge/skills/uhappylogic/cairn/finish-current-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.00040 | $0.01346 |
| Opus 5 | $0.00020 | $0.00673 |
| Sonnet 5 | $0.00008 | $0.00269 |
| Haiku 4.5 | $0.00004 | $0.00135 |
Grade A, and why
finish-current-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 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.
How it starts
The opening of the file, as written. The whole thing — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
finish-current-milestone
Wraps up the current milestone — verifies all tasks are done, records accomplishments in milestones/README.md, clears the current-milestone pointer to "none" in milestones/README.md, and updates CLAUDE.md only if the milestone introduced lasting changes to the project's environment context. It creates or modifies no files in <MILESTONE_DIR>/, and it never invokes /capture-milestone-principle-updates. Run this when all tasks are complete. After this, run /define-milestone-goal to define the next milestone, then /goto-next-milestone to activate it.
Usage
/finish-current-milestone
No arguments.
Workflow
1. Find the current milestone
Follow .agents/plugins/cairn/shared/get-current-milestone.md to resolve <MILESTONE_DIR> from the Current milestone: line in milestones/README.md. If the pointer is none, stop and tell the user there is no active milestone to finish.
Read <MILESTONE_DIR>/requirements.md and extract the milestone title from its top-level # Milestone N: <Title> heading (e.g. # Milestone 1: Public Release Preparation → title "Milestone 1 — Public Release Preparation"). The milestone number N comes from the path slug — strip any leading zeros when parsing it as an integer (e.g. milestone_01_foo → N is 1).
2. Read milestone content
Read in parallel:
<MILESTONE_DIR>/requirements.md— to extract the milestone Goal and key decisions.<MILESTONE_DIR>/TASKS_DONE.md— to list what was concretely built.
3. Verify the milestone is done
Check that <MILESTONE_DIR>/TASKS_TODO.md contains no ## sections. If tasks remain, stop and tell the user to complete them first (or move them to the next milestone).
4. Compose the completion summary
Write a short summary (3–8 bullet points) of what was accomplished. Draw from:
- The Goal section of
requirements.md - The completed tasks in
TASKS_DONE.md - Any significant decisions recorded in
requirements.md
Keep each bullet to one sentence, factual and grounded in the requirements and completed tasks — never an invented accomplishment. Focus on what now exists in the project, not on process.
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 Changed 4b6a3db37c12
- 5d ago Changed · -9 lines · -14 tokens per session 168378d0c176
- 10d ago First seen · 116 lines · 54 tokens per session scan A e3e89fee0d23
finish-current-milestone is a skill published in the GitHub repository uHappyLogic/cairn (2 stars, last pushed 2d ago), licensed MIT. It adds 40 tokens to every session and 1,346 once invoked, about $0.0002 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 (Opus) to ground the card cold — premise verify, aim validate, blast collect — and append a Verdict block — ## Verdict — auto-fix · {date} (Fix-shape / Probe-deps / Execution tags) or ## Verdict …
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…