Borrowing it
Nothing to install: this file belongs to bladeofgod/flutter-ai-harness. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/bladeofgod/flutter-ai-harness/main/.claude/commands/check-release.mdgit clone --depth 1 https://github.com/bladeofgod/flutter-ai-harnessWrote 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/bladeofgod/flutter-ai-harness/check-release)<a href="https://agentmods.dev/commands/bladeofgod/flutter-ai-harness/check-release"><img src="https://agentmods.dev/badge/commands/bladeofgod/flutter-ai-harness/check-release/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/bladeofgod/flutter-ai-harness/check-release"><img src="https://agentmods.dev/badge/commands/bladeofgod/flutter-ai-harness/check-release.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00012 | $0.00758 |
| Opus 5.5 | $0.00005 | $0.00303 |
| Sonnet 5.5 | $0.00002 | $0.00152 |
| Haiku 4.5 | $0.00001 | $0.00076 |
Grade A, and why
check-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 2mo 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
执行发版就绪检查。用户未明确要求时，不打 Tag、不上传、不发布、不 push。
检查项
- 确认发布范围和基线 Commit。
- 确认计划任务已完成或显式延后。
- 确认发布范围内的新任务普通 Review 格式为
routed-v1，其reviewProfiles与任务workKinds固定映射 一致，各 Profile 已有完成的独立结论且聚合 P0/P1 清零；既有 legacy 归档报告继续按历史格式兼容。 - 对声明
securityReview: required的任务确认security-<task-slug>.md已通过，并由make harness-check验证归档快照 metadata、依赖与产物结构。发版检查不要求全部历史 implementationDigest 匹配发布时的 当前文件，也不把历史快照解释为对后来内容的批准；本次发布范围的安全变化必须由对应的新活动任务、 Security Review、Evidence 和摘要覆盖。独立代码片段审查不能替代任务报告，未涉及安全边界的 发布不额外触发。 - 运行
make check和必要的代码生成同步检查。已有 UI Spec 只做 Schema 一致性检查，不要求 Audit 或 Run 齐全。 - 只有用户把某个 UI Spec 明确列入本次发布门禁时，才检查其 Audit、实现摘要和用户指定平台的 App Operator 报告；不得从任务卡或 Spec 的存在自动推导该门禁。
- 存在完整用户旅程或 Plugin/Bridge 改动时，使用
make integration-test INTEGRATION_DEVICE=<device-id>运行集成测试，并构建受影响平台；CI 的 Android/iOS Debug Job 必须通过。 - 检查 Bridge 契约版本和变更日志。
- 检查生成产物、依赖锁、发布配置、签名占位和敏感信息扫描。
- 检查用户可见变化、已知限制和回滚考虑。
产物
写报告前把版本解析为匹配 ^[a-z0-9]+(?:[.-][a-z0-9]+)*$ 的 lowercase 单段 token；拒绝斜杠、
反斜杠、空段、.、..、URI 编码、控制字符和其他可改变路径语义的输入。词法规范化
docs/reviews/release-<version>.md 后，必须确认目标仍是 docs/reviews/ 的直属路径，仓库根和
docs/reviews/ 都是非符号链接普通目录，且目标不存在。目标已经是文件、目录、符号链接或其他节点时
停止并要求新的版本标识；不得覆盖或追加任何已有任务报告、独立 Review 或历史发版报告。
检查通过后写入 docs/reviews/release-<version>.md，包含：
- 每个门禁的通过/失败结论。
- 精确命令证据。
- P0/P1 阻塞项。
- 延后风险和负责人。
- 本地未验证平台。
- 最终建议：可发布、有条件可发布或不可发布。
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.
- 2mo ago First seen · 42 lines · 12 tokens per session scan A 910cb22723cf
check-release is a command published in the GitHub repository bladeofgod/flutter-ai-harness (115 stars, last pushed 1mo ago), licensed MIT. It adds 12 tokens to every session and 758 once invoked, about $0.0000 per session on Opus 5.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
land
Resolve and squash merge one named, currently authorized pull request.
quality
A command for temporarily clearing a release quality gate or one named check, while recording the reason and expiry time. A quality gate is a required check that normally blocks completion or release.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
release-manager
Automated release coordination and deployment with ruv-swarm orchestration for seamless version management, testing, and deployment across multiple packages.
release-plan
A release-planning command for a software change. It documents the release scope, rollback plan, gradual or full rollout, and monitoring before waiting for human approval.
create-pr
Push the current branch and open a pull request into main with a structured description derived from the branch's commits and the open issues it resolves.