Borrowing it
Nothing to install: this file belongs to drakulavich/kesha-voice-kit. 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/drakulavich/kesha-voice-kit/main/.claude/skills/release-cli/SKILL.mdgit clone --depth 1 https://github.com/drakulavich/kesha-voice-kitWrote 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/drakulavich/kesha-voice-kit/release-cli)<a href="https://agentmods.dev/skills/drakulavich/kesha-voice-kit/release-cli"><img src="https://agentmods.dev/badge/skills/drakulavich/kesha-voice-kit/release-cli.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.1 | $0.00117 | $0.02456 |
| Opus 5 | $0.00059 | $0.01228 |
| Sonnet 5 | $0.00023 | $0.00491 |
| Haiku 4.5 | $0.00012 | $0.00246 |
Grade A, and why
release-cli 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 3d 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
release-cli
Cuts a CLI release. NEVER auto-runs — user invokes via /release-cli vX.Y.Z-cli.
For an engine release (bare vX.Y.Z, GitHub Release only) use the release-engine skill. A full ship is /release-engine first, then this one: the CLI release is what carries the new engine pin to users, and what ships the Linux packages.
Inputs
$1: target tag, e.g.v1.27.0-cli. The-climarker routes it:build-engine.ymlexcludes it,release-cli.ymlclaims it.
Stable versions only. cli-release-plan.mjs returns packages: false for anything with a prerelease identifier, which skips the packages job and — because publish-npm needs it — the npm dispatch too. A v1.28.0-beta.1-cli tag therefore does nothing at all while permanently consuming the name. Betas go through the legacy hand-cut path in release-mechanics; alphas have their own lane and no GitHub release.
What the tag sets off
Pushing vX.Y.Z-cli runs 🚀 Release (CLI), which in one run:
- classifies the tag and refuses one that already has a release;
- builds and verifies the Linux
.deb/.rpm; - creates the marker release as a draft carrying those packages plus
SHA256SUMS, then un-drafts it; - dispatches
📦 npm Publishand waits for it, then verifies the version is on npm.
Steps 2–4 must happen together: the .deb is named from package.json#version, and nothing downstream re-checks that npm ever served it since #727 removed the assertion that did.
A human has to push the tag. A GITHUB_TOKEN push fires no on.push.tags — which is exactly why the alpha lane's own -cli tags never reach this workflow, alphas having no GitHub release by design.
Do not npm publish from a laptop. npm-publish.yml is the one entry workflow npm's trusted publisher accepts (#731), and it publishes with provenance from an OIDC identity. Un-drafting from a workflow raises no release: published, so the dispatch is explicit rather than cascading.
Cut one stable CLI release at a time. npm-publish.yml's concurrency: queue: max serialises runs but does not order them by version, so two stable markers in flight can finish out of order and leave latest on the older one.
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.
- 3d ago Changed 0413376477da
- 7d ago First seen · 154 lines · 117 tokens per session scan A aba0f53f747e
release-cli is a skill published in the GitHub repository drakulavich/kesha-voice-kit (73 stars, last pushed today), licensed MIT. It adds 117 tokens to every session and 2,456 once invoked, about $0.0006 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
ship
Ship workflow: detect + merge base branch, run tests, review diff, bump VERSION, update CHANGELOG, commit, push, create PR. Use when asked to "ship", "deploy", "push to main", "create a PR", "merge and push", or "get it deployed". Proactively invoke this skill (do NOT push/PR directly) when the user says code is…
benchmark
Run performance + quality benchmarks. ASR reports WER, RTF, process memory, and throughput across engines/variants. Arguments include asr, tts, vad, diarize, asr-quick.
review-pr
Review a pull request for conceptual fit, architecture impact, adversarial failure modes, security risk, docs impact, regression risk, test coverage, and merge readiness. Use when asked to review a PR, check whether a PR is safe to merge, decide if more tests are needed, perform adversarial or security review, or…
commit-pr
Mandatory Codex/Copilot publication adapter for opencode-swarm. Use for every GitHub issue assignment that results in code changes, commits, pushes, draft PRs, PR body edits, PR readying, release notes, or CI closeout. Must be loaded before git push, gh pr create, gh pr edit, or gh pr ready. Routes to the single…
contributing
Codex adapter for the opencode-swarm contribution checklist. Use when preparing user-visible changes, release note fragments, local validation, branch hygiene, PR checklist items, or contribution-policy compliance before publishing work.
release-aur
Use when creating, updating, reviewing, or publishing Arch User Repository (AUR) packages. Runs /release-aur plan first, reviews PKGBUILD/.SRCINFO/build/namcap evidence, and only recommends /release-aur publish after a GO decision.