Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add uHappyLogic/cairn/plugin install 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/answer-open-question)<a href="https://agentmods.dev/skills/uhappylogic/cairn/answer-open-question"><img src="https://agentmods.dev/badge/skills/uhappylogic/cairn/answer-open-question.svg" alt="Measured on agentmods" 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.00025 | $0.01283 |
| Opus 5 | $0.00013 | $0.00642 |
| Sonnet 5 | $0.00005 | $0.00257 |
| Haiku 4.5 | $0.00003 | $0.00128 |
Grade A, and why
answer-open-question 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
answer-open-question
Resolves a named open or deferred question in the current milestone's requirements.md by recording the user's answer, propagating its implications through the document, and committing that edit on its own with the decision's rationale in the commit body — establishing the Manual-answer: commit the finish-time /capture-milestone-principle-updates skill later distills into reusable principles. The answer text is recorded literally; the one reserved answer text is the retired sentinel record the recommendation, which this skill redirects instead of recording (step 2).
Usage
/answer-open-question <Short Title>. <answer text>
The <Short Title> must match (case-insensitive, against the block's id) an existing <open-question status="open|deferred"> block. The . character is the separator. Everything after the first . is the answer.
Example (literal answer):
/answer-open-question Getting-started section order. Use approach B — open the "Draft the Getting Started section of the user guide" deliverable with the install-and-run walkthrough, then follow it with the conceptual overview, so a new reader reaches a working setup before the background material.
Example (retired sentinel — redirected, records nothing):
/answer-open-question Getting-started section order. record the recommendation
Workflow
1. Parse the input
Split the skill args on the first . character:
- Before: the question Short Title (trim whitespace)
- After: the answer text (trim whitespace)
If no . is found, report a parse error and show the expected format.
2. Redirect guard for the retired sentinel
Compare the parsed answer text — trimmed and lowercased — against the retired sentinel record the recommendation, as an exact whole-string match (never a substring: an answer that merely contains those words is a literal answer, not the sentinel). This is a pure string comparison on the parsed text — no milestone resolution, no file read.
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 · -11 lines · -5 tokens per session f2a53e7dd8e7
- 5d ago First seen · 83 lines · 30 tokens per session scan A 5763804c7fc8
answer-open-question is a skill published in the GitHub repository uHappyLogic/cairn (2 stars, last pushed yesterday), licensed MIT. It adds 25 tokens to every session and 1,283 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
codex-thread-orchestration
Use when running Arcgentic V2 in Codex and the current thread must orchestrate fixed Planner, Developer, Test, and Auditor role threads.
claude-code-session-broker
Use when running Arcgentic V2 in Claude Code and fixed Planner, Developer, and Auditor role sessions must be coordinated through a broker.
arcgentic
Use when the user says Arcgentic, asks to use Arcgentic, or wants an idea taken through a complete plan → development → self-audit → external audit workflow in Codex.
audit-round
External-audit role for arcgentic rounds. Loaded when arcgentic state.yaml is in awaitingaudit or auditinprogress, OR when the user explicitly requests an external audit of a finished round, OR when reviewing a handoff doc + commit chain against the round's declared scope. Produces a PASS / NEEDSFIX / AUDITINCOMPLETE…
session-mode
Use when a project has not yet stored session mode, when a user asks for complete arcgentic workflow execution, or when role identity handoff prompts are needed.
verify-gates
Runs the mechanical quality gates that the arcgentic state machine requires for state transitions. Invoked indirectly by transition.sh OR directly by orchestrator agent before declaring a state transition. Use when about to call transition.sh OR when manually verifying that a round artifact meets the gate criteria.…