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 specify-milestone-starting-stategit 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/specify-milestone-starting-state)<a href="https://agentmods.dev/skills/uhappylogic/cairn/specify-milestone-starting-state"><img src="https://agentmods.dev/badge/skills/uhappylogic/cairn/specify-milestone-starting-state/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/specify-milestone-starting-state"><img src="https://agentmods.dev/badge/skills/uhappylogic/cairn/specify-milestone-starting-state.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.00036 | $0.01051 |
| Opus 5 | $0.00018 | $0.00526 |
| Sonnet 5 | $0.00007 | $0.00210 |
| Haiku 4.5 | $0.00004 | $0.00105 |
Grade A, and why
specify-milestone-starting-state 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
specify-milestone-starting-state
Reads the milestone goal, explores the project's existing state, and writes a concise summary into the ## Relevant starting state section of requirements.md. The output is reference material — not decisions — to ground the ## Decisions conversation that follows.
Usage
/specify-milestone-starting-state <milestone_id>
<milestone_id>: the milestone directory name undermilestones/, e.g.milestone_12_user-guide.
Example:
/specify-milestone-starting-state milestone_12_user-guide
Workflow
1. Locate the milestone
Resolve milestones/<milestone_id>/requirements.md. If the file does not exist, stop and report that the milestone was not found — suggest running /define-milestone-goal first.
2. Read the goal
Read requirements.md in full. Extract the ## Goal section. This is the lens for everything that follows — only surface starting state that is directly relevant to achieving or building on that goal.
3. Load the environment and explore the project
Read CLAUDE.md at the workspace root for the project's environment. If it carries no description of the project's domain context or working conventions, suggest the user run /init to enrich it first — richer project context yields a sharper starting-state summary — then proceed with whatever the project reveals.
Extract from CLAUDE.md:
- The project's domain context — what the project is and how its material is organized; use this to anchor all exploration
- Working conventions — the practices the project follows
- Available tools — whether any tools (including MCP tools) are available for deeper inspection
- How work is verified as done — the project's convention for confirming a deliverable meets its bar
Using the goal as a filter, investigate the areas the project documents in CLAUDE.md. Focus on:
- Existing artifacts relevant to the goal — find the artifacts, sections, and components whose names or responsibilities overlap with the goal. Read what they expose — their outward-facing surface. Skip internal detail.
- Existing capabilities — if the goal builds on something that already exists, describe its current state and how other work connects to it.
- Supporting materials — note any settings, reference data, or structures the milestone will likely touch.
- Known gaps — if the goal requires something that clearly does not exist yet, state it as a gap in one sentence and move on; do not design its replacement here.
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 d4ee9c8c0ad7
- 5d ago Changed · -7 lines acff6abd557c
- 10d ago First seen · 103 lines · 36 tokens per session scan A 4171f67358d3
specify-milestone-starting-state is a skill published in the GitHub repository uHappyLogic/cairn (2 stars, last pushed 2d ago), licensed MIT. It adds 36 tokens to every session and 1,051 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-init
Write or refresh a "Tech debt operations" section in the project's AGENTS.md so the team shares one source of truth for debt-ops disciplines. Run ONLY when the user explicitly asks to set up, install, or initialize debt-ops disciplines — never auto-invoke. Idempotent; only the managed section changes, other sections…
debt-ops-metrics
Print a debt-ops health summary from the metrics log, covering registration rate, feedback action rate, ADR creation, and AI-authored share. Use when the user asks for "debt-ops metrics", "debt health", "registry stats", or a tech-debt health summary. Read-only, never writes the log.
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…
review
Run a full code review on current changes or specified files. Runs ruff lint, review-code agent, and security scan in sequence.
plan-task
Structured task planning using Work files. Use for any new feature, bug fix, or project that needs a task breakdown before implementation.
scout-consolidation
Launch a Scout consolidation session as a background process. Runs a lighter delta scan — captures what changed since the last run and updates action items and KB.