Borrowing it
Nothing to install: this file belongs to SolaceProducts/solace-broker-mcp. 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/SolaceProducts/solace-broker-mcp/main/.claude/skills/cut-release/SKILL.mdgit clone --depth 1 https://github.com/SolaceProducts/solace-broker-mcpWrote 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/solaceproducts/solace-broker-mcp/cut-release)<a href="https://agentmods.dev/skills/solaceproducts/solace-broker-mcp/cut-release"><img src="https://agentmods.dev/badge/skills/solaceproducts/solace-broker-mcp/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/solaceproducts/solace-broker-mcp/cut-release"><img src="https://agentmods.dev/badge/skills/solaceproducts/solace-broker-mcp/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.00098 | $0.05295 |
| Opus 5 | $0.00049 | $0.02648 |
| Sonnet 5 | $0.00020 | $0.01059 |
| Haiku 4.5 | $0.00010 | $0.00530 |
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 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 — 298 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cut a release
Run the whole release from one command. Invoked with /cut-release <version> (or "cut a new
v0.6.0 release").
The release pipeline (.github/workflows/release.yml) triggers on a pushed v* tag and does the
heavy lifting itself — builds binaries for 4 OS/arch, pushes the multi-arch image, extracts the
tagged commit's ## [X.Y.Z] CHANGELOG block, and creates the GitHub Release from it with
artifacts + checksums attached. No GitHub-UI "draft release / auto-generate notes" step is needed.
So cutting a release reduces to: get the dated CHANGELOG block onto main, then push the tag.
The one human checkpoint is merging the changelog PR — that is where "make sure the changelog
is updated properly" happens, and it is required because main is protected and the pipeline reads
the CHANGELOG from the tagged commit. Everything before and after is automatic: the merge is
treated as the go-ahead, and the tag fires on merge (guarded — see Phase D).
Usage
/cut-release <version>— e.g./cut-release 0.6.0orv0.6.0.
Validate first: reject anything not matching ^v?[0-9]+\.[0-9]+\.[0-9]+$ (stable SemVer) before
any command uses the value. Then normalize once and derive both forms explicitly: strip a leading
v for the bare form (0.6.0) used in the ## [0.6.0] heading and wherever the Phase D awk
takes v="0.6.0"; keep the v-prefixed form (v0.6.0) for the git tag and compare-URL
segments. Never pass the raw argument through un-normalized (a v0.6.0 input must not yield
## [v0.6.0] or a vv0.6.0 tag).
Preconditions: run gh auth status up front. Phases B–E (open/watch the PR, tag, report)
require an authenticated gh — if it's unavailable, stop and have the operator run
gh auth login before those phases. Phase A2 alone can degrade to a git log fallback when gh is
missing (less precise — see A2), so preparation may proceed unauthenticated, but the release cannot
be cut without gh.
Phase A — Prepare the changelog
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 · 298 lines · 98 tokens per session scan A 9eba553713e4
cut-release is a skill published in the GitHub repository SolaceProducts/solace-broker-mcp (11 stars, last pushed yesterday), licensed Apache-2.0. It adds 98 tokens to every session and 5,295 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-30.
Other skills, from other repositories
conventional-git
Conventional Commits v1.0.0 branch naming and commit message standards for GitHub and GitLab projects. Use when creating branches, writing commits, generating commit messages, reviewing branch conventions, or setting up changelog automation. Apply when your project needs consistent git history, SemVer-driven releases…
octocat
Handles git and GitHub operations using the gh CLI. Use when the user asks about pull requests (PRs), GitHub issues, repo management, branching, merging, rebasing, cherry-picking, merge conflict resolution, commit history cleanup, pre-commit hook debugging, GitHub Actions workflows, or releases. Covers creating and…
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.