Borrowing it
Nothing to install: this file belongs to heygen-com/heygen-cli. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/heygen-com/heygen-cli/main/.agents/skills/release-cli/SKILL.mdgit clone --depth 1 https://github.com/heygen-com/heygen-cliWrote 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/heygen-com/heygen-cli/release-cli)<a href="https://agentmods.dev/skills/heygen-com/heygen-cli/release-cli"><img src="https://agentmods.dev/badge/skills/heygen-com/heygen-cli/release-cli/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/heygen-com/heygen-cli/release-cli"><img src="https://agentmods.dev/badge/skills/heygen-com/heygen-cli/release-cli.svg" alt="Reviewed on agentmods" width="80" 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.00115 | $0.01898 |
| Opus 5.5 | $0.00046 | $0.00759 |
| Sonnet 5.5 | $0.00023 | $0.00380 |
| Haiku 4.5 | $0.00012 | $0.00190 |
Grade A, and why
release-cli scanned grade A with 1 finding 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 21d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
`install.sh` reads `INSTALL_DIR`, so it goes on `bash`, not `curl`: `d=$(mktemp -d); curl -fsSL https://static.heygen.ai/cli/install.sh | INSTALL_DIR="$d" bash`, How it starts
The opening of the file, as written. The whole thing — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release the heygen CLI
RELEASE.md is the source of truth for every step below; this skill runs it in order and adds where to stop and what tends to go wrong. When the two disagree, RELEASE.md wins, and fix this file.
Work from a fresh fetch, never from the local main checkout, which may be
behind. Set LAST_STABLE and RELEASE_COMMIT exactly as RELEASE.md's pre-release
checklist shows and keep them for the whole run: RELEASE_COMMIT is what every
step checks and what stop 4 releases. If a merge at step 2 moves origin/main,
fetch, set RELEASE_COMMIT again, and redo from step 1.
Stop points
Stop and ask the user before each of these, with what you found and a
recommendation. Never proceed on a guess. Each stop needs an explicit yes for
that specific action, in this session: the original request, a yes at an earlier
stop, or silence does not count. The one exception is stop 4, whose yes also
covers publishing its notes. If the action changes after the yes (a new head
after a rebase, a different commit on main, edited notes), ask again.
- Changing any open PR before the release (step 2): pushing to it (examples
for a sync PR, a rebase onto
main), approving it, or merging it. - Running E2E (step 5): it spends API credits and needs
HEYGEN_API_KEY. Ask which key to use; do not go looking for one. - The version (step 6), whenever step 4 found anything breaking or you are unsure between patch and minor.
- Triggering the release workflow. Show the version,
RELEASE_COMMIT, and the notes file step 9 will publish (a dev release has none), and record itsshasum -a 256. Dispatch with-f commit=<that SHA>so the workflow releases exactly that commit. A yes here also covers publishing that file at step 9 for this version. - Replacing the published release notes (step 9), unless re-running
shasum -a 256on the file then matches the hash recorded at the most recent stop 4 yes in this session for this version: show the final notes. A lost hash means asking. - Any recovery action (step 8) that changes the repository or a release: deleting a tag or release, dispatching again, or re-running a job. Say which job failed, what RELEASE.md prescribes, and what the action will change.
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.
- 21d ago Changed · +6 lines 06dd77ab7401
- 22d ago First seen · 140 lines · 115 tokens per session scan A 2839ad0e890a
release-cli is a skill published in the GitHub repository heygen-com/heygen-cli (164 stars, last pushed today), licensed Apache-2.0. It adds 115 tokens to every session and 1,898 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-08.
Other skills, from other repositories
release
Release preparation workflow - security audit → E2E tests → review → changelog → docs.
release-pr-quality-gate
Build an AgentWorks release or pull-request browser quality gate over saved suites and exact build identity. Use when a merge, deployment, or promotion needs an auditable QA decision.
release-validation
The final "Green Light". Checks all test suites (Unit, Int, E2E) and third-party reports.
test-next-release
Smoke-test the @next npm release against the petstore example — installs globally, sets up session auth, and verifies all CRUD operations work end-to-end.
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.
github
Drive GitHub via the official gh CLI — repos, issues, pull requests, releases, gists, Actions runs, and raw REST through gh api. Use when the user asks to inspect or manage GitHub.