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/byte-n/larkdocx2md/release-versionnpx skills add Byte-n/larkDocx2md --skill release-versiongit clone --depth 1 https://github.com/Byte-n/larkDocx2mdWrote 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/byte-n/larkdocx2md/release-version)<a href="https://agentmods.dev/skills/byte-n/larkdocx2md/release-version"><img src="https://agentmods.dev/badge/skills/byte-n/larkdocx2md/release-version.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.00059 | $0.00707 |
| Opus 5 | $0.00030 | $0.00353 |
| Sonnet 5 | $0.00012 | $0.00141 |
| Haiku 4.5 | $0.00006 | $0.00071 |
Grade A, and why
release-version 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
Release Version Workflow
严格按序执行，每步执行完简短反馈；需用户决策的节点（提交改动、确认版本号、同名分支复用）必须等待确认。
版本号规则
任何版本段（major/minor/patch）的十进制字符串含字符 4 即跳过。例：
0.3.3 → 0.3.5、0.3.9 → 0.5.0、0.13 → 0.15、0.39 → 0.50、3 → 5
等级判定：feat/新 API → minor；fix/文档/测试 → patch；破坏性变更 → major。
流程
1. 检查工作区：git status --porcelain。有改动则建议 commit 命令（feat/fix/docs/test/chore + 中文简短描述）并询问是否提交。
2. 汇总变更：
git describe --tags --abbrev=0
git log <last-tag>..HEAD --oneline --no-decorate
按 Features / Changed / Fixed / Removed 分组，面向用户可见行为。
3. 确定新版本号：按上述规则计算，与用户确认。
4. 切版本分支：git checkout -b release/v<版本>。同名分支存在先确认；用 git branch --show-current 验证。
5. 更新 CHANGELOG.md：在 # Changelog 下方插入新段落，风格对齐已有版本：
## <版本>
### Features
- **要点**：...
无该类变更则省略小节；中文描述；不写时间戳。
6. 评估 README.md：从本次 Features/Changed 中提取面向用户可见的功能点与新特性，对照 README.md 现有内容判断是否需要更新（如新增功能介绍、用法示例、配置项、CLI 参数、兼容性说明等）。
- 需更新：列出具体改动点并与用户确认后再修改。
- 无需更新（仅内部重构/测试/文档微调）：简短说明理由后跳过。
7. 更新 package.json：仅改 "version" 字段。
8. 提交：
git add CHANGELOG.md package.json README.md
git commit -m "release: <版本>"
（若 README.md 未改动则从 git add 中省略。）
9. 构建：pnpm run build。失败立即停止。
10. 输出发布命令（不自动执行）：
git push -u origin release/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.
- 4d ago First seen · 60 lines · 59 tokens per session scan A da15370b3f18
release-version is a skill published in the GitHub repository Byte-n/larkDocx2md (31 stars, last pushed 20d ago), licensed ISC. It adds 59 tokens to every session and 707 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
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-entry
Add a new entry to CHANGELOG.yml under the current unreleased version (or create the version block if needed), then regenerate documentation. Use when the user says things like "add a changelog entry", "log this fix in the changelog", or "/changelog-entry".
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
mate-oss-gate
在准备把 MateCloud（或其子集）开源 / 发布到公开仓前使用。按 open-core 边界把关：剥离企业代码、清竞品名与内部路径、查密钥、确认 LICENSE。当用户说"要开源了""发布公开版""开源前检查""oss release"时触发。.
snapshot-release
Drives the snapshot-release flow for the current branch's PR. Posts a /snapshot comment on the PR if one isn't already there (with confirmation), waits for the Continuous Releases workflow to finish, and reports the tarball URLs from the resulting 📦 Snapshot Release comment. Use for both triggering and waiting …
devops/changelog-generation
自动生成 CHANGELOG，基于 git 提交历史和 pipeline 产物信息，遵循 Conventional Commits 和 Keep a Changelog 规范.