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/hrygo/hotplex-legacy/hotplex-releasenpx skills add hrygo/hotplex-legacy --skill hotplex-releasegit clone --depth 1 https://github.com/hrygo/hotplex-legacyWrote 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/hrygo/hotplex-legacy/hotplex-release)<a href="https://agentmods.dev/skills/hrygo/hotplex-legacy/hotplex-release"><img src="https://agentmods.dev/badge/skills/hrygo/hotplex-legacy/hotplex-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.00036 | $0.01337 |
| Opus 5 | $0.00018 | $0.00668 |
| Sonnet 5 | $0.00007 | $0.00267 |
| Haiku 4.5 | $0.00004 | $0.00134 |
Grade A, and why
hotplex-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.
How it starts
The opening of the file, as written. The whole thing — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
HotPlex Release Skill
Complete release automation: version bump → changelog → git commit → tag → push → CI verify → GitHub release.
When to Use
Triggered by: "发布版本", "创建 release", "版本升级", "打 tag", "发布新版本", "bump version"
NOT for: Regular commits, non-release git operations
Quick Reference
| Operation | Command |
|---|---|
| Current version | grep 'Version = ' hotplex.go |
| Last tag | git describe --tags --abbrev=0 |
| Commits since last tag | git log --oneline $(git describe --tags --abbrev=0)..HEAD |
| CI status | gh run list --limit 3 |
| Create release | gh release create vX.Y.Z --title "vX.Y.Z" --notes-file CHANGELOG.md |
Release Workflow
Step 1: 确定发布参数
用户未指定发布类型时，明确询问：
- patch (v0.31.9 → v0.32.0): Bug fixes
- minor (v0.31.9 → v0.32.0): New features
- major (v0.31.9 → v1.0.0): Breaking changes
Step 2: 前置验证
必须通过后才继续：
# 确保工作区干净
git status
# 运行测试
go test ./...
go test -race ./...
# Lint
go vet ./...
Step 3: 版本号递增
必须更新全部 5 个文件，缺一不可：
| # | File | Field |
|---|---|---|
| 1 | hotplex.go |
Version = "vX.Y.Z" |
| 2 | Makefile:64 |
VERSION = X.Y.Z |
| 3 | CHANGELOG.md |
Header entry |
| 4 | CLAUDE.md:3 |
vX.Y.Z |
| 5 | AGENT.md:3 |
vX.Y.Z |
版本计算：
- patch:
x.y.Z+1 - minor:
x.y+1.0 - major:
x+1.0.0
Step 4: 生成 CHANGELOG
从 git log 自动获取自上次 tag 以来的所有提交：
git log --oneline $(git describe --tags --abbrev=0)..HEAD
按 Conventional Commits 归类到 ### Features / ### Bug Fixes / ### Maintenance：
## [vX.Y.Z] - YYYY-MM-DD
### Features
- feat(scope): description (PR #)
### Bug Fixes
- fix(scope): description (PR #)
### Maintenance
- chore(scope): description (PR #)
Step 5: Git 操作
git add -A
git commit -m "chore(release): bump version to vX.Y.Z"
git push origin main
git tag -a vX.Y.Z -m "Release vX.Y.Z"
git push origin vX.Y.Z
Step 6: CI 验证
Tag push 后立即验证 CI：
gh run list --limit 3
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 · 178 lines · 0 tokens per session scan A 87280ba9a124
hotplex-release is a skill published in the GitHub repository hrygo/hotplex-legacy (11 stars, last pushed 4mo ago), licensed MIT. It adds 36 tokens to every session and 1,337 once invoked, about $0.0002 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
Generic release assistant — analyzes repo release rules, caches them in .omc/RELEASERULE.md, then guides the release.
cmux-release
Prefer the /release command. It determines the new version (minor by default), gathers commits since the last tag, updates CHANGELOG.md, runs ./scripts/bump-version.sh, commits, runs ./scripts/release-pretag-guard.sh, then tags and pushes.
hotplex-release
通过判断 SemVer 影响、整理 CHANGELOG、对账版本面和验证发布输入来准备或发布 HotPlex 版本。不要用于主机二进制更新、运行时诊断或文档巡逻。.
deploy-automation
Workflows and best practices for CI/CD automation, deployment strategies, and production releases. Use when implementing or improving deployment pipelines, managing environments, or planning production releases.
publish-package-cicd
CI/CD publishing workflow for npm packages using Changesets + npm Trusted Publishers (OIDC). Use when setting up automated npm publishing for monorepos, configuring GitHub Actions for releases, troubleshooting workspace: protocol resolution issues, fixing "Cannot find module" errors in published packages, or debugging…
team-release
Orchestrate the release team: coordinates release-manager, qa-lead, devops-engineer, and producer to execute a release from candidate to deployment.