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 define-milestone-goalgit 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/define-milestone-goal)<a href="https://agentmods.dev/skills/uhappylogic/cairn/define-milestone-goal"><img src="https://agentmods.dev/badge/skills/uhappylogic/cairn/define-milestone-goal/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/define-milestone-goal"><img src="https://agentmods.dev/badge/skills/uhappylogic/cairn/define-milestone-goal.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.00030 | $0.01020 |
| Opus 5 | $0.00015 | $0.00510 |
| Sonnet 5 | $0.00006 | $0.00204 |
| Haiku 4.5 | $0.00003 | $0.00102 |
Grade A, and why
define-milestone-goal 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
define-milestone-goal
Creates a new milestone directory under milestones/ with a requirements.md pre-filled with the goal, plus empty TASKS_TODO.md and TASKS_DONE.md. Does not populate the remaining sections — those are filled by subsequent skills (/specify-milestone-starting-state, /review-milestone-requirements, etc.). Defining a milestone does not activate it: this skill never updates CLAUDE.md or milestones/README.md, which change only when the milestone becomes the current active one via /goto-next-milestone.
Usage
/define-milestone-goal <overall_goal_description>
<overall_goal_description>: a clear description of what the milestone should accomplish. Use/discuss-milestone-goalfirst if the goal is still vague.
Example:
/define-milestone-goal add a getting-started guide that walks a new user through their first session
Workflow
1. Determine the milestone number
Scan the milestones/ directory for subdirectories whose names match the pattern milestone_<NN>_* (e.g. milestone_01_public-release-prep). For each matching directory, extract the numeric prefix and parse it as an integer, stripping any leading zeros (01 → 1, 09 → 9). Take the maximum integer found and add 1 to get the next milestone number. Format the result zero-padded to two digits (e.g. 1 → 01, 9 → 09, 10 → 10).
If milestones/ contains no matching directories (cold start), treat the maximum as 0, so the first milestone number is 1, formatted 01.
Do not read the milestone number from CLAUDE.md or from milestones/README.md's pointer — the scan is the sole source.
2. Derive the milestone slug
Convert <overall_goal_description> to a short kebab-case slug (3–5 words max) that captures the essence of the goal. The full directory name is milestone_<NN>_<slug> where <NN> is the zero-padded two-digit number from step 1.
Example: "add a getting-started guide that walks a new user through their first session" → milestone_12_getting-started-guide (if the next number happens to be 12)
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 4531f3587031
- 5d ago Changed · -7 lines 2abd01341d52
- 10d ago First seen · 102 lines · 30 tokens per session scan A 98b2f25e504d
define-milestone-goal is a skill published in the GitHub repository uHappyLogic/cairn (2 stars, last pushed 2d ago), licensed MIT. It adds 30 tokens to every session and 1,020 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…