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/release-plangit 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/release-plan)<a href="https://agentmods.dev/commands/alisunstar/opensunstar/release-plan"><img src="https://agentmods.dev/badge/commands/alisunstar/opensunstar/release-plan.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.00123 |
| Opus 5 | $0.00000 | $0.00062 |
| Sonnet 5 | $0.00000 | $0.00025 |
| Haiku 4.5 | $0.00000 | $0.00012 |
Grade A, and why
release-plan 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:release-plan — 发布计划
阶段 6b：发布前计划与检查。
先读
.specs/<change-id>/REVIEW.md.specs/<change-id>/IMPLEMENTATION-CHECK.md
执行
- 发布范围确认
- 回滚方案
- 灰度/全量策略
- 监控项确认
产物
.specs/<change-id}/RELEASE-PLAN.md
人工确认
是 — 发布计划需人工确认后执行发布。
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 · 20 lines · 0 tokens per session scan A e2baa860963f
release-plan is a command published in the GitHub repository alisunstar/OpenSunstar (40 stars, last pushed 20d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 123 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
update-changelog-and-tag
You are preparing a release. Follow these steps precisely.
release
This document describes the standard release process for agtrace.
mach12:pr-create
Create a pull request for the current branch with structured description.
mach12:pr-merge
Merge a PR, delete the feature branch, and optionally create a release.
lavra-ship
Fully automated ship sequence from code-ready to PR-open with beads closed and knowledge captured.
changelog
Create engaging changelogs for recent merges to main branch.