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-requirementgit 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-requirement)<a href="https://agentmods.dev/commands/alisunstar/opensunstar/verify-requirement"><img src="https://agentmods.dev/badge/commands/alisunstar/opensunstar/verify-requirement.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.00157 |
| Opus 5 | $0.00000 | $0.00078 |
| Sonnet 5 | $0.00000 | $0.00031 |
| Haiku 4.5 | $0.00000 | $0.00016 |
Grade A, and why
verify-requirement 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 5d 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-requirement — 契约确认
阶段 3：确认应用级 requirement 契约，编码前最后门禁。
先读
.specs/<change-id>/DECOMPOSITION.md.specs/<change-id>/applications/{app}/requirement.md
执行
- 逐应用确认 requirement 契约可执行
- 校验验收标准可测、边界清晰
何时停止
- 契约不可执行 → 停止，回 decompose 修正
产物
无（门禁确认，不产文件）
人工确认
是 — 契约确认后才能进入 apply 编码。
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.
- 5d ago First seen · 21 lines · 0 tokens per session scan A 297d21e02319
verify-requirement is a command published in the GitHub repository alisunstar/OpenSunstar (40 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 157 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
ask
Ask a natural-language question about the repository and get an evidence-backed answer.
ingest-pr
Command "ingest-pr" from Avos-Lab/git-aware-coding-agent, covering avos ingest-pr, usage, description, arguments and options.
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-history
Get chronological history of a subject in the repository.