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/validate)<a href="https://agentmods.dev/commands/alisunstar/opensunstar/validate"><img src="https://agentmods.dev/badge/commands/alisunstar/opensunstar/validate/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/validate"><img src="https://agentmods.dev/badge/commands/alisunstar/opensunstar/validate.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.00403 |
| Opus 5.5 | $0.00000 | $0.00161 |
| Sonnet 5.5 | $0.00000 | $0.00081 |
| Haiku 4.5 | $0.00000 | $0.00040 |
Grade A, and why
validate 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:validate — 五状态对账
阶段 5：对照 requirement 契约，校验实现完成度，产接续产物。
先读规则
- 读
.specs/<change-id>/applications/{app}/requirement.md（契约） - 读
.specs/<change-id>/DECOMPOSITION.md（拆解清单） - 读当前代码实现（知识提供上下文，代码是事实）
执行
逐项对照契约，标注五状态：
- done — 已实现且符合契约
- partial — 部分实现，有缺口
- todo — 未开始
- changed — 实现偏离契约（需确认是否更新契约）
- blocked — 被阻塞，需外部输入
何时澄清
changed项需确认：是更新契约还是修正实现blocked项需外部输入
何时停止
- 存在
blocked项 → 停止，等外部输入 changed项未确认 → 停止，等人工裁决
产物
.specs/<change-id>/IMPLEMENTATION-CHECK.md（五状态对账表 + 汇总 + 后续行动）.specs/<change-id>/CONTINUE-PROMPT.md（跨会话接续：当前进度 + 关键上下文 + 未决问题 + 接续指令）
人工确认
是 — 产出对账结果后暂停，等人工确认后继续 code-review 或回 apply 修复。
95% 原则
不追求 100% 全 AI——剩下两行手改更快就手改，不必强求对账全 done。
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 · 42 lines · 0 tokens per session scan A 41d1dc9ce763
validate 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 403 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.