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.
npx agentmods add commands/alisunstar/opensunstar/verify-prdgit 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/verify-prd)<a href="https://agentmods.dev/commands/alisunstar/opensunstar/verify-prd"><img src="https://agentmods.dev/badge/commands/alisunstar/opensunstar/verify-prd.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00339 |
| Opus 5 | $0.00000 | $0.00169 |
| Sonnet 5 | $0.00000 | $0.00068 |
| Haiku 4.5 | $0.00000 | $0.00034 |
Grade A, and why
verify-prd 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 4d 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:verify-prd — 输入质量门禁
阶段 0：校验 PRD/需求输入质量，fail-fast 暴露早期问题。
先读规则
- 读
.specs/<change-id>/已有产物（若有） - 读
knowledge/ROUTING.md定位需求所属业务域 - 读
knowledge/main/对应域的公共语境
执行
校验输入是否满足以下质量门槛：
- 需求目标明确（做什么、为什么、成功标准）
- 范围边界清晰（包含什么、不包含什么）
- 关键约束识别（性能/兼容/安全/历史包袱）
- 验收标准可测
何时澄清
- 目标模糊或冲突 → 暂停，产出待澄清项
- 范围缺失 → 暂停，要求补充
何时停止
- 输入质量不达标 → 停止，不进入分析
- 缺少关键约束 → 停止，要求补充
产物
.specs/<change-id>/CHANGE.md（需求输入摘要 + 质量评估 + 待澄清项）
人工确认
是 — 产出 CHANGE.md 后暂停，等人工确认质量达标后继续。
fail-fast 原则
能在 PRD 阶段暴露的问题，绝不拖到 requirement 或编码阶段。
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.
- 4d ago First seen · 40 lines · 0 tokens per session scan A eaae16d811ff
verify-prd is a command published in the GitHub repository alisunstar/OpenSunstar (40 stars, last pushed 3d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 339 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
ingest-pr
Command "ingest-pr" from Avos-Lab/git-aware-coding-agent, covering avos ingest-pr, usage, description, arguments and options.
ask
Ask a natural-language question about the repository and get an evidence-backed answer.
history
Get a chronological history of a subject or topic in the repository.
hook-install
Install a git hook for automatic commit sync on push. When installed, every git push automatically syncs pushed commits to Avos Memory, enabling real-time team synchronization.
avos-ask
Search repository memory for engineering context.
avos-ingest-pr
Ingest a single PR into repository memory.