clarify

A command for resolving unanswered questions in a product requirement before technical analysis. It records the questions and agreed answers in a clarification document.

In plain words
What is it for?
It reads the open questions in a change document, works through them one by one, and saves the answers for the next planning stage.
Why use it?
It prevents developers from having to guess what the requirement means or make decisions that should be confirmed by a person.

Command

Install

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.

agentmods
npx agentmods add commands/alisunstar/opensunstar/clarify
Clone the repo
git clone --depth 1 https://github.com/alisunstar/OpenSunstar
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 119 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00119
Opus 5 $0.00000 $0.00060
Sonnet 5 $0.00000 $0.00024
Haiku 4.5 $0.00000 $0.00012

Measured 3d ago against content hash 2fbae47cf29c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

clarify 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.

rd-protocol/commands/clarify.md · 16 lines

What it actually says

/rd:clarify — 澄清

阶段 1a:对 verify-prd 产出的待澄清项逐条澄清。

先读

  • .specs/<change-id>/CHANGE.md(待澄清项)

执行

  • 逐条澄清待澄清项,记录问答

产物

  • .specs/<change-id>/clarification.md

人工确认

— 澄清结果需人工确认后继续 analyze。

Changes

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.

  1. 3d ago First seen · 16 lines · 0 tokens per session scan A 2fbae47cf29c

Subscribe to this mod's changes

clarify is a command published in the GitHub repository alisunstar/OpenSunstar (40 stars, last pushed 20d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 119 tokens. 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-30.