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 recommend-all-open-questionsgit 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/recommend-all-open-questions)<a href="https://agentmods.dev/skills/uhappylogic/cairn/recommend-all-open-questions"><img src="https://agentmods.dev/badge/skills/uhappylogic/cairn/recommend-all-open-questions/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/recommend-all-open-questions"><img src="https://agentmods.dev/badge/skills/uhappylogic/cairn/recommend-all-open-questions.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.00027 | $0.05065 |
| Opus 5 | $0.00014 | $0.02533 |
| Sonnet 5 | $0.00005 | $0.01013 |
| Haiku 4.5 | $0.00003 | $0.00507 |
Grade A, and why
recommend-all-open-questions 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 — 340 lines — stays where its author put it; the contents beside it link to each section on GitHub.
recommend-all-open-questions
This is the non-interactive batch path for producing recommendations on open questions. It
walks every open and deferred question in the current milestone most-significant-first,
strictly one at a time, and, per question, dispatches a read-only subagent — the
non-interactive twin of /discuss-open-question — that returns alternatives + a single
recommendation as the <open-question> block's XML sub-elements. The orchestrator is the
sole document mutator: it embeds each returned set of sub-elements inside the existing
<open-question> block before dispatching the next question, leaving the block's
<open-question …> / </open-question> boundary tags and its <question> element untouched,
so every later recommendation may build on the sibling recommendations already embedded and
declares each such use as a <depends-on question="…" option="…"/> child of its block. It is
argument-free, records no decisions, and triggers no cascades — it only annotates.
Each embedded recommendation is consumed later, when it is recorded as an answer, by
/answer-open-question-with-recommendation or the
/answer-all-open-questions-with-recommendation sweep.
Usage
/recommend-all-open-questions
Takes no arguments — it sweeps every <open-question> block (both status="open" and
status="deferred") in the current milestone's requirements.md.
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. Gather the questions once
Fetch the open/deferred set with the line-oriented boundary-line CLI. Every <open-question>
block lives under the single ## Open questions section of <MILESTONE_DIR>/requirements.md,
so that section is the one bounded region the CLI slices deterministically. Using awk/sed/grep
keyed on the <open-question …> opening and </open-question> closing boundary lines — never
a real XML processor (xmllint) — enumerate every block in document order and, for each, extract
its id and status (by attribute-name-anchored regex like id="([^"]*)" and status="([^"]*)",
so extraction is independent of attribute order) and its <question> text. Open and deferred
blocks share one <open-question …> / </open-question> boundary-token pair distinguished only by
status, so the gather ignores type — it lists them all. If there are none, say so and stop.
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 · +51 lines 6e0e616bd8de
- 2d ago Changed · +98 lines 405d58172b63
- 4d ago Changed · +28 lines 73087a4213a2
- 6d ago Changed · -52 lines · -147 tokens per session ffa0c66aadb1
- 11d ago First seen · 215 lines · 174 tokens per session scan A 5de2fd46f23c
recommend-all-open-questions is a skill published in the GitHub repository uHappyLogic/cairn (2 stars, last pushed today), licensed MIT. It adds 27 tokens to every session and 5,065 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-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.