Borrowing it
Nothing to install: this file belongs to adamayoung/TMDb. 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/adamayoung/TMDb/main/.claude/skills/cut-release/SKILL.mdgit clone --depth 1 https://github.com/adamayoung/TMDbWrote 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/adamayoung/tmdb/cut-release)<a href="https://agentmods.dev/skills/adamayoung/tmdb/cut-release"><img src="https://agentmods.dev/badge/skills/adamayoung/tmdb/cut-release/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/adamayoung/tmdb/cut-release"><img src="https://agentmods.dev/badge/skills/adamayoung/tmdb/cut-release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00075 | $0.03093 |
| Opus 5 | $0.00037 | $0.01546 |
| Sonnet 5 | $0.00015 | $0.00619 |
| Haiku 4.5 | $0.00007 | $0.00309 |
Grade A, and why
cut-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 9d 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 — 250 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cut Release
Takes main from "a pile of merged PRs" to "a tagged, published release".
This skill is never headless. Every other skill in this repo may decide for
itself; this one may not. A tag is the one artifact consumers resolve against,
and publishing one is effectively irreversible: SwiftPM hands a new minor or
patch to everyone inside the current from: range the moment it exists, a new
major reaches everyone who has since bumped, and deleting a tag does not
un-fetch it from anyone who already resolved. Phases 1–5 are read-only and local.
Phase 6 is a hard stop. Phases 7–9 run only on an explicit go-ahead.
If invoked with no human able to answer, run to the hard stop, print the summary, and exit. Do not tag.
Phase 1 — Preflight
Stop on any failure; report which one and what to do.
- On
main, clean tree, in sync withorigin/main(git status --porcelain,git rev-list --count main..origin/main). git fetch --tags; establish the last release:git tag --sort=-v:refname | head -1.- CI is green on the current
maintip:gh api repos/adamayoung/TMDb/commits/<sha>/check-runs. This is the entry check — the commit that actually gets tagged does not exist yet (Phase 7 creates it), and Phase 7 re-checks that one. Starting from a redmainjust means finding out later. - There is something to release — at least one commit since the last tag that is not purely a tag-housekeeping commit.
Phase 2 — Work out the version
Two independent signals. They must agree, or you stop.
Signal A — the CHANGELOG (authoritative). The open ## [X.Y.Z] section at
the top (no date = unreleased) is the proposal. Count **Breaking:** markers
inside it, and read the section headings:
- any
**Breaking:**→ major - otherwise any
### Addedcontent → minor - otherwise (
### Fixed/### Changedonly) → patch
Signal B — the commits (cross-check). git log <lasttag>..HEAD, bucketed by
gitmoji. Consumer-visible: ✨ feature, 🐛 fix, ♻️ refactor, 🔒 security,
⚡️ perf. Not consumer-visible: 🔧 chore, 📝 docs, 👷 CI, ✅ tests,
📦 build. Count multibyte-safely — sort | uniq -c over emoji collapses
distinct ones in a non-UTF-8 locale and will hand you a confidently wrong tally.
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.
- 9d ago First seen · 250 lines · 75 tokens per session scan A b4a078876a75
cut-release is a skill published in the GitHub repository adamayoung/TMDb (176 stars, last pushed 9d ago), licensed Apache-2.0. It adds 75 tokens to every session and 3,093 once invoked, about $0.0004 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
releasing-plugin-versions
Use when releasing a new plugin version, bumping versions, creating git tags, or publishing GitHub releases for this marketplace.
ios-bump-version
An iOS release helper for changing an app's marketing version, the version number shown to users, and committing the change on the appropriate branch. It first checks the version format, Git state, branch, and current version.
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.