validate

A progress check that compares the current code with the written requirement and labels each part as done, partial, todo, changed, or blocked.

In plain words
What is it for?
It checks application requirements against the task breakdown and code, then creates an implementation report and a handoff prompt for continuing later.
Why use it?
It shows exactly what is complete, missing, different from the plan, or waiting on outside information, so unfinished work is not mistaken for finished work.

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/validate
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 403 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.00403
Opus 5 $0.00000 $0.00201
Sonnet 5 $0.00000 $0.00081
Haiku 4.5 $0.00000 $0.00040

Measured yesterday against content hash 41d1dc9ce763, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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

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/validate.md · 42 lines

What it actually says

/rd:validate — 五状态对账

阶段 5:对照 requirement 契约,校验实现完成度,产接续产物。

先读规则

  1. .specs/<change-id>/applications/{app}/requirement.md(契约)
  2. .specs/<change-id>/DECOMPOSITION.md(拆解清单)
  3. 读当前代码实现(知识提供上下文,代码是事实)

执行

逐项对照契约,标注五状态:

  • 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。

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. yesterday First seen · 42 lines · 0 tokens per session scan A 41d1dc9ce763

Subscribe to this mod's changes

validate is a command published in the GitHub repository alisunstar/OpenSunstar (40 stars, last pushed 18d 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.