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.
git clone --depth 1 https://github.com/alisunstar/OpenSunstarWrote 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/commands/alisunstar/opensunstar/clarify)<a href="https://agentmods.dev/commands/alisunstar/opensunstar/clarify"><img src="https://agentmods.dev/badge/commands/alisunstar/opensunstar/clarify/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/commands/alisunstar/opensunstar/clarify"><img src="https://agentmods.dev/badge/commands/alisunstar/opensunstar/clarify.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.00000 | $0.00119 |
| Opus 5.5 | $0.00000 | $0.00048 |
| Sonnet 5.5 | $0.00000 | $0.00024 |
| Haiku 4.5 | $0.00000 | $0.00012 |
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 1mo 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.
What it actually says
/rd:clarify — 澄清
阶段 1a：对 verify-prd 产出的待澄清项逐条澄清。
先读
.specs/<change-id>/CHANGE.md（待澄清项）
执行
- 逐条澄清待澄清项，记录问答
产物
.specs/<change-id>/clarification.md
人工确认
是 — 澄清结果需人工确认后继续 analyze。
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.
- 1mo ago First seen · 16 lines · 0 tokens per session scan A 2fbae47cf29c
clarify is a command published in the GitHub repository alisunstar/OpenSunstar (31 stars, last pushed 3d 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.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
memorize
Pins a decision, insight or convention to the vault right away. /save already does this automatically at the end of the session; use this command only when you want to write something now, mid-session.
speckit.opsmill.retrospect
Run a session retrospective that surfaces context-management gaps and routes them to approved follow-up actions.
pr
Handle the full workflow from current branch state to an open, CI-monitored pull request.
create-issue
Transform feature descriptions, bug reports, or improvement ideas into well-structured GitHub issues.
mach12:gh-pr-read
Read a GitHub pull request's title, body, and all top-level PR conversation comments; optionally locate an HTML-marker comment.