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/work)<a href="https://agentmods.dev/commands/alisunstar/opensunstar/work"><img src="https://agentmods.dev/badge/commands/alisunstar/opensunstar/work/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/work"><img src="https://agentmods.dev/badge/commands/alisunstar/opensunstar/work.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.00503 |
| Opus 5.5 | $0.00000 | $0.00201 |
| Sonnet 5.5 | $0.00000 | $0.00101 |
| Haiku 4.5 | $0.00000 | $0.00050 |
Grade A, and why
work 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:work — 路由命令（唯一入口）
通用路由命令：根据用户输入与当前 .specs// 状态，自动推断意图并引导下一步。使用者事实上只需输入这一个命令。
先读规则
- 读
STATE.md（active change）与.specs/<change-id>/已有产物清单 - 读 knowledge/ROUTING.md（若存在）建立业务定位
- 对照 rd-loop 阶段链：0-verify-prd → 1-clarify-analyze → 2-decompose → 3-verify-requirement → 4-apply → 5-validate → 6-review-release → 7-backfill
执行
按以下顺序推断下一步并给出「命令 + 推荐提示词」：
| 当前状态 | 引导下一步 |
|---|---|
| 无 CHANGE.md | /rd:verify-prd（输入质量门禁） |
| 有 CHANGE.md，无 ANALYSIS.md | /rd:clarify 或 /rd:analyze |
| 有 ANALYSIS.md，无 DECOMPOSITION.md | /rd:decompose |
| 有 DECOMPOSITION/REQUIREMENT，未确认 | /rd:verify-requirement（人工确认） |
| 契约已确认，未实现 | /rd:apply |
| 已实现，无 IMPLEMENTATION-CHECK.md | /rd:validate（五状态对账） |
| 对账已确认，无 REVIEW.md | /rd:code-review |
| REVIEW 已确认 | /rd:release-plan，随后 /rd:backfill 收尾 |
何时澄清
- 用户输入无法唯一映射到阶段时，列出候选并暂停等选择。
何时停止
- 任一上游门禁未通过（verify-prd / verify-requirement / validate 存在 blocked 或未确认 changed）→ 停止并指向对应门禁，不自动绕过。
产物
- 无新增产物；本命令只产出「下一步引导」。
人工确认
否（引导本身不改变状态；被引导到的命令按其自身矩阵确认）。
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 · 41 lines · 0 tokens per session scan A f34250907282
work is a command published in the GitHub repository alisunstar/OpenSunstar (31 stars, last pushed 14d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 503 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.
speckit.opsmill.retrospect
Run a session retrospective that surfaces context-management gaps and routes them to approved follow-up actions.
create-issue
Transform feature descriptions, bug reports, or improvement ideas into well-structured GitHub issues.
pr
Handle the full workflow from current branch state to an open, CI-monitored pull request.
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.
scramjet:troubleshoot
Diagnose unexpected command behavior and recommend safe resolution.