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/xiaobei930/cc-best/releasegit clone --depth 1 https://github.com/xiaobei930/cc-bestWhat 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.00015 | $0.00938 |
| Opus 5 | $0.00008 | $0.00469 |
| Sonnet 5 | $0.00003 | $0.00188 |
| Haiku 4.5 | $0.00002 | $0.00094 |
Grade A, and why
release 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 3d 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
/release - 版本发布管理
管理插件版本发布流程，自动同步版本号到所有相关文件，更新 CHANGELOG，创建 Git Tag。
使用方式
# 发布补丁版本 (0.5.9 → 0.5.10)
/cc-best:release patch
# 发布次版本 (0.5.9 → 0.6.0)
/cc-best:release minor
# 发布主版本 (0.5.9 → 1.0.0)
/cc-best:release major
# 预览变更（不实际执行）
/cc-best:release patch --dry-run
# 指定版本号
/cc-best:release 0.6.0
执行流程
第 0 步：守卫检查
git status必须干净（无未提交变更）- 当前分支必须是
main - 确认远程仓库已同步（
git pull --ff-only） - 检查 CHANGELOG.md 中是否有待发布内容
第 1 步：读取当前版本
# 从 plugin.json 读取版本
node -e "console.log(require('./.claude-plugin/plugin.json').version)"
第 2 步：计算目标版本
根据参数计算下一版本号：
| 当前版本 | patch | minor | major |
|---|---|---|---|
| 0.5.9 | 0.5.10 | 0.6.0 | 1.0.0 |
第 3 步：同步版本号
需要更新版本号的文件（4 个）：
| 文件 | 字段/位置 |
|---|---|
.claude-plugin/plugin.json |
version 字段 |
.claude-plugin/marketplace.json |
plugins[0].version 字段 |
.claude-plugin/ARCHITECTURE.md |
头部 Version: x.x.x |
CHANGELOG.md |
[x.x.x] - YYYY-MM-DD 标题 |
同时更新 plugin.json 中 description 的统计数字（如有变化）。
第 4 步：更新 CHANGELOG
- 将
[x.x.x] - YYYY-MM-DD替换为实际日期 - 如有
Unreleased区段，合并到新版本区段 - 确保格式符合 Keep a Changelog 规范
第 5 步：提交与打标签
# 提交版本变更
git add -A
git commit -m "chore(release): v<VERSION>"
# 创建标签
git tag -a v<VERSION> -m "Release v<VERSION>"
第 6 步：验证
- 确认 4 个文件版本号一致
- 确认 Git Tag 已创建
- 确认 CHANGELOG 格式正确
- 提示用户执行
git push && git push --tags（不自动推送）
--dry-run 模式
预览模式下：
- 显示将要修改的文件和内容
- 显示版本号变化:
0.5.9 → 0.6.0 - 不实际修改任何文件
- 不创建 commit 或 tag
注意事项
- 不自动推送: 发布后提示用户手动推送，给予最后确认机会
- 幂等性: 如果中途失败，可以重新执行（会覆盖上次的部分变更）
- CHANGELOG 格式: 严格遵循 Keep a Changelog 格式
- 语义化版本: 遵循 SemVer 规范
记住: 发布是一个仪式——版本号、CHANGELOG、tag 缺一不可。发布前检查比发布后修复成本低十倍。
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.
- 3d ago First seen · 114 lines · 15 tokens per session scan A ae9acfeab1a6
release is a command published in the GitHub repository xiaobei930/cc-best (50 stars, last pushed 2mo ago), licensed MIT. It adds 15 tokens to every session and 938 once invoked, about $0.0001 per session on Opus 5. 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
release
Release a new version. Bumps version, updates docs/site/changelog, tags, pushes, and updates the marketplace repo.
release
Bump version, commit, tag, and push to trigger the release workflow.
ship
Ship workflow — detect base branch, merge, run tests, review diff, bump VERSION, update CHANGELOG, commit, push, create PR.
document-release
Post-ship documentation update — reads all project docs, cross-references the diff, updates README/ARCHITECTURE/CONTRIBUTING/CLAUDE.md to match what shipped.
release-doctor
Verify the Plumbline version is current and self-consistent (VERSION equals the latest GitHub release equals the CLI), dogfood plumbline update --check, and confirm README claims are derived not stale. For is-the-github-version-up-to-date and are-all-claims-correct checks.
lfe-archivist
Act as the Archivist for an LFE-compliant project. Use when a change is approved and needs documentation sync, changelog updates, or pipeline status cleanup.