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 review-milestone-requirementsgit 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/review-milestone-requirements)<a href="https://agentmods.dev/skills/uhappylogic/cairn/review-milestone-requirements"><img src="https://agentmods.dev/badge/skills/uhappylogic/cairn/review-milestone-requirements/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/review-milestone-requirements"><img src="https://agentmods.dev/badge/skills/uhappylogic/cairn/review-milestone-requirements.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.02656 |
| Opus 5 | $0.00018 | $0.01328 |
| Sonnet 5 | $0.00007 | $0.00531 |
| Haiku 4.5 | $0.00004 | $0.00266 |
Grade A, and why
review-milestone-requirements 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 today.
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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
review-milestone-requirements
The current "work in progress" requirements for the planned milestone live in the current milestone's requirements.md. The overall goal is to make that file ready enough for the work to begin — it's fine to leave some decisions to settle while doing the work if they're better solved there.
This skill is the repeatable engine of the requirements-iteration loop — run it each time around:
review → (discuss) → answer → review → answer → … → converged → derive-tasks
Each pass does three jobs: reconcile the existing questions against what's now decided, surface the new gaps, and report whether the document has converged.
review-milestone-requirements
/review-milestone-requirements
Milestone requirements document structure
The structure of requirements.md is as follows:
# Milestone <milestone_id>: <name>
## Goal
<description of the goal here>
## Relevant starting state
<description of the Relevant starting state>
## Decisions
<subsections with detailed requirements>
## Open questions
<any open questions, each a `<open-question>` XML block>
The ## Goal, ## Relevant starting state, ## Decisions, and ## Out of Scope sections stay prose Markdown. The ## Open questions section is different: it holds raw, structured <open-question> XML blocks (one per question, never inline next to a requirement), queried by line-oriented CLI (awk/sed/grep on the block boundary lines). All <open-question> blocks live under this one section.
Workflow
0. Find the current milestone
Follow .agents/plugins/cairn/shared/get-current-milestone.md to resolve <MILESTONE_DIR>. Never use a hardcoded path.
1. Read the document and take inventory
Read <MILESTONE_DIR>/requirements.md in full. Build a mental inventory of three things, because the rest of the pass plays them against each other:
- the Decisions already recorded (what's settled),
- the
<open-question>blocks already present under## Open questions(what's still flagged) — bothstatus="open"andstatus="deferred", - every stated requirement, constraint, and assumption.
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.
- today Changed · +2 lines 51e58b31067d
- 5d ago Changed 0230fb658371
- 6d ago Changed · -9 lines · -161 tokens per session c09ee6b38556
- 11d ago First seen · 147 lines · 197 tokens per session scan A b6da3454564d
review-milestone-requirements is a skill published in the GitHub repository uHappyLogic/cairn (2 stars, last pushed yesterday), licensed MIT. It adds 36 tokens to every session and 2,656 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-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…
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.
multi-perspective-review
Multi-perspective collaborative review of plans or documents. Ten expert viewpoints deliberate in 3 rounds to reach consensus.
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.