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/killvxk/pm-skills-zh/release-notesnpx skills add killvxk/pm-skills-zh --skill release-notesgit clone --depth 1 https://github.com/killvxk/pm-skills-zhWrote 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/killvxk/pm-skills-zh/release-notes)<a href="https://agentmods.dev/skills/killvxk/pm-skills-zh/release-notes"><img src="https://agentmods.dev/badge/skills/killvxk/pm-skills-zh/release-notes.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.00074 | $0.00690 |
| Opus 5 | $0.00037 | $0.00345 |
| Sonnet 5 | $0.00015 | $0.00138 |
| Haiku 4.5 | $0.00007 | $0.00069 |
Grade A, and why
release-notes 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
发布说明生成器
将技术工单、PRD（产品需求文档）或内部变更日志转化为精致的面向用户发布说明。
Context（背景）
你正在为 $ARGUMENTS 编写发布说明。
如果用户提供了文件（JIRA 导出、Linear 工单、PRD、Git 日志或内部变更日志），请先阅读。如果他们提到产品 URL，可使用网络搜索了解产品和受众。
Instructions（操作指南）
-
收集原始素材：阅读所有提供的工单、变更日志或描述，提取：
- 变更了什么（功能、改进或修复）
- 影响了哪些用户（哪个用户群体）
- 为什么重要（用户收益）
-
对变更进行分类：
- 新功能：全新的能力
- 改进：对现有功能的增强
- 缺陷修复：已解决的问题
- 破坏性变更：任何需要用户采取行动的内容（迁移、API 变更）
- 废弃说明：即将下线的功能
-
遵循以下原则撰写每个条目：
- 以用户收益为先，而非技术变更
- 使用通俗语言——避免行话、内部代号或工单编号
- 每个条目控制在 1-3 句话
- 如果用户提供了视觉稿或截图，附上
转化示例：
-
技术描述："为仪表板 API 端点实现 Redis 缓存层"
-
用户版本："仪表板加载速度提升最高 3 倍，让你花更少时间等待，更多时间分析数据。"
-
技术描述："修复并发结账流程中的竞态条件"
-
用户版本："修复了在高流量期间部分订单可能失败的问题。"
-
结构化发布说明：
# [产品名称] — [版本 / 日期] ## 新功能 - **[功能名称]**：[1-2 句话描述功能内容及重要性] ## 改进 - **[改进方向]**：[什么变得更好了，以及如何帮助用户] ## 缺陷修复 - 修复了 [用户语言描述的问题] ## 破坏性变更（如有） - **需要操作**：[用户需要做什么] -
调整语气以匹配产品的声音——B2B 产品专业严谨，消费者产品亲切友好，API 产品以开发者为中心。
保存为 Markdown 文档。如果用户需要 HTML 或其他格式，相应转换。
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 · 64 lines · 74 tokens per session scan A 31971897a6bc
release-notes is a skill published in the GitHub repository killvxk/pm-skills-zh (151 stars, last pushed 5mo ago), licensed MIT. It adds 74 tokens to every session and 690 once invoked, about $0.0004 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
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
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.
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…