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 rules/zhangdszq/teamclaw/release-tagginggit clone --depth 1 https://github.com/zhangdszq/teamclawWrote 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/rules/zhangdszq/teamclaw/release-tagging)<a href="https://agentmods.dev/rules/zhangdszq/teamclaw/release-tagging"><img src="https://agentmods.dev/badge/rules/zhangdszq/teamclaw/release-tagging.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.00299 | $0.00299 |
| Opus 5 | $0.00150 | $0.00150 |
| Sonnet 5 | $0.00060 | $0.00060 |
| Haiku 4.5 | $0.00030 | $0.00030 |
Grade A, and why
release-tagging 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
发版流程
每次发新版本必须按以下顺序操作：
# 1. 更新 package.json 版本号
sed -i '' 's/"version": "x.x.x"/"version": "x.x.y"/' package.json
# 2. 提交版本号变更
git add package.json
git commit -m "chore: bump version to x.x.y"
# 3. 打 tag
git tag vx.x.y
# 4. 推送（本仓库常用远端名 `teamclaw`）
git push teamclaw main && git push teamclaw vx.x.y
推送 v* tag 后，GitHub Actions CI & Release 会打包并发布到 GitHub Releases（无需阿里云；可选配置 OSS 再传对象存储）。也可使用脚本：./scripts/release-github.sh x.x.y（要求工作区干净）。
❌ 禁止
- 不能先打 tag 再改版本号
- 不能 force push 已有 tag（GitHub Actions 可能不重新触发）
- 不能跳过 package.json 更新（应用内显示版本来自 package.json，不是 git 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.
- 4d ago First seen · 32 lines · 299 tokens per session scan A 63d021dc18ae
release-tagging is a cursor rule published in the GitHub repository zhangdszq/teamclaw (113 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 299 tokens to every session, about $0.0015 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 cursor rules, from other repositories
shared-memory
Keep the shared project memory file up to date across all AI agents.
gsd-ship-labels
After /gsd-ship creates a PR, always run gsd-ship-post (labels + optional changeset).
release-checklist
What to update with each code change or version release.
release-policy
Release, versioning, and signing policy for setmac.
github-repo-triage
Triage and maintain GitHub repos — issues, PRs, cherry-picks, releases, publishing.
release
Automated release workflow — versioning, changelog generation, tagging.