Borrowing it
Nothing to install: this file belongs to thomas-powers-jr/cadence. 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/thomas-powers-jr/cadence/main/.claude/skills/release-cut/SKILL.mdgit clone --depth 1 https://github.com/thomas-powers-jr/cadenceWrote 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/thomas-powers-jr/cadence/release-cut)<a href="https://agentmods.dev/skills/thomas-powers-jr/cadence/release-cut"><img src="https://agentmods.dev/badge/skills/thomas-powers-jr/cadence/release-cut/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/thomas-powers-jr/cadence/release-cut"><img src="https://agentmods.dev/badge/skills/thomas-powers-jr/cadence/release-cut.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.00092 | $0.01385 |
| Opus 5 | $0.00046 | $0.00692 |
| Sonnet 5 | $0.00018 | $0.00277 |
| Haiku 4.5 | $0.00009 | $0.00138 |
Grade A, and why
release-cut 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 10d 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release cut
Publishing is irreversible. Two hard consent gates in this flow: merging the release PR, and firing the Release workflow. Neither happens on a generic "continue" — restate the action and get an explicit go-ahead.
1 — Inventory what ships
git fetch origin --prune, thengit log $(git describe --tags --abbrev=0)..origin/main --oneline --no-merges.- Map commits to phases; write the bundle list (this becomes the PR body and the CLAUDE.md version-line summary).
- Audit changesets: every feature PR in the bundle should have left a
.changeset/*.md. For any missing one (discipline has slipped before — five had to be reconstructed retroactively for v1.42.0), reconstruct it from the PR description now, and note the slip in the handoff.
2 — Version bump (lockstep)
- On a release branch:
pnpm changeset:version. - Verify all four published packages (
core,types,host-claude-code,host-codex) moved to the identical new version andtestkitdid not. Anything else is a stop-and-investigate. - Update the version line near the top of
CLAUDE.mdto the new version string. The doc-sync pre-commit hook aborts the commit otherwise, andpackages/core/tests/docs/doc-sync-hook.test.tsre-asserts it in CI. - Add a matching
## [x.y.z]heading toCHANGELOG.mdfor the new version, in the same commit. The same doc-sync pre-commit hook now checks CHANGELOG.md too — it aborts the commit if the newest heading doesn't match — andpackages/core/tests/docs/doc-sync-hook.test.tshas a seconddescribeblock that re-asserts it in CI. - Run the full pipeline locally:
pnpm turbo run lint typecheck test build.
3 — Doc-sync verification (mandatory, not implied by the pipeline run)
Step 2's full pipeline only proves the automated doc-content tests pass —
it does not prove every doc mentioning the old version got updated, since
several repo docs (DESIGN.md, docs/*) carry version references with no
test covering them.
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.
- 10d ago First seen · 104 lines · 92 tokens per session scan A 2210b711a13d
release-cut is a skill published in the GitHub repository thomas-powers-jr/cadence (2 stars, last pushed yesterday), licensed MIT. It adds 92 tokens to every session and 1,385 once invoked, about $0.0005 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-31.
Other skills, from other repositories
release-expert
Multi-repo release coordination: version alignment, RC lifecycle, release waves, rollback planning. Use when saying "release", "version alignment", or "cut an RC".
release-clisbot
Release clisbot safely to npm and GitHub. Use when Codex is asked to prepare, validate, bump, publish, tag, or document a clisbot beta release, next beta release, or official stable/latest release, including release notes, migration notes, GitHub release notes, npm dist-tags, and post-publish verification.
git-workflow
Use when naming or scoping a branch, writing or fixing a commit message, picking the gitmoji for a commit, untangling history (rebase versus merge versus squash), or cutting a versioned release — the portable git-convention layer for any repo. Covers gitmoji + Conventional Commits, SemVer tags, branch hygiene…
agentplane-release-and-packaging-operator
Use when preparing, validating, publishing, auditing, or recovering an Agentplane release, especially package build ordering, version parity, npm/GitHub/GHCR/external distribution publication, public install smoke tests, hosted publish evidence, or release CI failures.
release
Prepare code for release (version bumps, changelog, README updates) and create an annotated tag to trigger the GoReleaser workflow.
argot-setup
Set argot up for a repository end to end — audit its history, decide what should shape its voice, fit, verify the fit actually catches things, tune the rules its own history says are noisy, and wire the places it runs (pre-write hook, pre-commit, MCP, CI). One sitting, one decision at a time, each proposed with the…