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/timzaak/web-dev-skills/t-releasenpx skills add timzaak/web-dev-skills --skill t-releasegit clone --depth 1 https://github.com/timzaak/web-dev-skillsWrote 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/timzaak/web-dev-skills/t-release)<a href="https://agentmods.dev/skills/timzaak/web-dev-skills/t-release"><img src="https://agentmods.dev/badge/skills/timzaak/web-dev-skills/t-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 | $0.00019 | $0.00508 |
| Opus 5 | $0.00010 | $0.00254 |
| Sonnet 5 | $0.00004 | $0.00102 |
| Haiku 4.5 | $0.00002 | $0.00051 |
Grade A, and why
t-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 5d 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 commit 和 git tag，并推送到远程。
版本号使用语义化版本，如 0.2.0、1.0.0。版本文件写入纯版本号 X.Y.Z，最终 git tag 必须使用 vX.Y.Z 格式。用户输入 0.2.0 或 v0.2.0 时，都按版本号 0.2.0 发布，并创建 tag v0.2.0。
执行流程
使用发布脚本，不要手工拼接 release 命令。优先用项目自带的脚本，仓库没有才用插件的：
- 仓库根目录存在
scripts/release.py→ 用项目脚本：python scripts/release.py [版本号] - 没有项目脚本 → 用插件脚本：
uv run ${CLAUDE_PLUGIN_ROOT}/scripts/release.py [版本号]
如果用户未提供版本号，先不带参数运行脚本获取推荐版本（在报错输出里），用户确认后再带版本号执行。
两个脚本接口一致，都负责：
- 检查
main分支、干净工作区、远程可访问、tag 不冲突。 - 更新各自清单内的版本文件（项目脚本以仓库实际为准）。
- 运行验证，创建 commit
chore: bump version to <版本号>，创建并推送 tagv<版本号>。
失败处理
- 按脚本错误输出处理。
- 验证失败时终止，不创建 commit/tag。
- 推送失败时提示用户本地 commit/tag 状态和手动推送命令。
Forbidden
- 绕过上述发布脚本手工执行发布。
- 创建或推送不带
v前缀的 release tag。 - 使用
--force推送。
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.
- 5d ago First seen · 49 lines · 19 tokens per session scan A dd56a39832e6
t-release is a skill published in the GitHub repository timzaak/web-dev-skills (69 stars, last pushed today), licensed Apache-2.0. It adds 19 tokens to every session and 508 once invoked, about $0.0001 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
finishing-a-development-branch
当实现完成、所有测试通过、需要决定如何集成这份工作时使用.
release-archivist
Close out a spec-superflow change with verification, summary, and archive readiness. Invoke when implementation is complete, verification is underway, or the user asks for a final wrap-up.
github-release
Guides IA through releasing a new version of a GitHub library end-to-end. Handles SemVer versioning and Keep a Changelog formatting automatically.
mlops-collaboration
Prepare a project for public collaboration — license, code of conduct, docs, branch rulesets, templates, and git-cliff releases. Use when open-sourcing a repository, onboarding contributors, or cutting a tagged release.
create-github-pull-request-from-specification
Create GitHub Pull Request for feature request from specification file using pullrequesttemplate.md template.
ship
Take a finished local change through verification, UI checks, pull-request publication, CI and review follow-up, and the user-authorized merge outcome. Use when implementation is complete and the user says "ship it" or "get this merged," or as the final stage of $build. Do not use to implement new feature scope.