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 skills/linfee/spec-kit-cn/spec-kit-releasenpx skills add Linfee/spec-kit-cn --skill spec-kit-releasegit clone --depth 1 https://github.com/Linfee/spec-kit-cnWrote 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/skills/linfee/spec-kit-cn/spec-kit-release)<a href="https://agentmods.dev/skills/linfee/spec-kit-cn/spec-kit-release"><img src="https://agentmods.dev/badge/skills/linfee/spec-kit-cn/spec-kit-release.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.1 | $0.00057 | $0.00644 |
| Opus 5 | $0.00028 | $0.00322 |
| Sonnet 5 | $0.00011 | $0.00129 |
| Haiku 4.5 | $0.00006 | $0.00064 |
Grade A, and why
spec-kit-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 6d 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
Spec Kit 对齐发布流程
严格约束：版本号必须与 spec-kit 对齐，不允许自增自定义版本。
1) 确认目标版本
- 从
./spec-kit获取上游最新 tag（如v0.1.10）。 - 本项目发布版本必须使用同一个 tag。
2) 合并到主分支并校验
- 若当前不在
main，先合并到main。 - 推送
main前完成本地发布校验（项目已有脚本优先）：
bash tests/e2e/validate-release.sh
- 校验通过后推送
main。
3) 首次发布（正常路径）
git tag vX.Y.Z
git push origin vX.Y.Z
推送 tag 后应触发 release.yml。
4) 同版本重发（失败补救路径）
当同版本发布失败且必须保持版本不变时，按顺序执行：
- 修复问题并合并到
main。 - 删除远端 release（若存在）：
gh release delete vX.Y.Z --repo Linfee/spec-kit-cn --yes
- 删除远端 tag（若存在）：
git push origin :refs/tags/vX.Y.Z
- 删除本地 tag（若存在）：
git tag -d vX.Y.Z
- 推送修复后的
main，重新打并推送同名 tag：
git push origin main
git tag vX.Y.Z
git push origin vX.Y.Z
5) 发布后验收
- GitHub Actions:
release.yml最新运行必须completed/success。 - Release 状态：非 draft、非 prerelease。
- 资产清单：与
github/spec-kit对应版本 release 资产列表一致（agent/script 组合一致）。
可用检查命令：
gh run list --repo Linfee/spec-kit-cn --workflow release.yml --limit 5
gh release view vX.Y.Z --repo Linfee/spec-kit-cn --json url,tagName,isDraft,isPrerelease
gh release view vX.Y.Z --repo Linfee/spec-kit-cn --json assets --jq '.assets[].name' | sort
gh release view vX.Y.Z --repo github/spec-kit --json assets --jq '.assets[].name' | sort
若资产命名仅版本前缀（v）策略不同，需确认组合与数量完全一致。
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.
- 6d ago First seen · 82 lines · 57 tokens per session scan A 941692b38411
spec-kit-release is a skill published in the GitHub repository Linfee/spec-kit-cn (695 stars, last pushed 1mo ago), licensed MIT. It adds 57 tokens to every session and 644 once invoked, about $0.0003 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 skills, from other repositories
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
release
Cut a Symphony release by bumping the committed version, landing it, tagging the merged commit, and verifying the Burrito release workflow. Use when asked to release, tag, or retag Symphony.
changelog
Create changelog files for important commits in a PR.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
refresh-arm-sdk-release
WORKFLOW SKILL — Prepares Azure.ResourceManager SDK refresh pull requests in azure-sdk-for-net. WHEN: "prepare sdk refresh", "refresh Azure.ResourceManager package", "update ARM SDK from autorest tag", "refresh changelog dependencies". INVOKES: git and GitHub pull request tools for branch, commit, push, and PR…