Borrowing it
Nothing to install: this file belongs to lewing/helix.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/lewing/helix.mcp/main/.squad/skills/release-cut/SKILL.mdgit clone --depth 1 https://github.com/lewing/helix.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/lewing/helix.mcp/release-cut)<a href="https://agentmods.dev/skills/lewing/helix.mcp/release-cut"><img src="https://agentmods.dev/badge/skills/lewing/helix.mcp/release-cut.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.00000 | $0.01466 |
| Opus 5 | $0.00000 | $0.00733 |
| Sonnet 5 | $0.00000 | $0.00293 |
| Haiku 4.5 | $0.00000 | $0.00147 |
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 7d 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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SKILL: Cutting a Release for helix.mcp
When to use
Use this skill whenever Larry asks to cut a release (e.g., "prep vX.Y.Z release").
Pre-flight checks
- Confirm the target version (
vMAJOR.MINOR.PATCH). - Identify the current
origin/maintip SHA — the branch must be cut from there. - Read
.squad/agents/ripley/history.mdfor any notes on the previous release process.
Step 1 — Branch
git fetch origin
git checkout -b release/vX.Y.Z origin/main
Never branch from a local main that may have diverged.
Step 2 — Version bump (exactly 3 occurrences)
The publish.yml workflow validates all three match the pushed tag. Any mismatch aborts the release.
| File | Field | Example |
|---|---|---|
src/HelixTool/HelixTool.csproj |
<Version> |
<Version>0.8.0</Version> |
src/HelixTool/.mcp/server.json |
top-level "version" |
"version": "0.8.0" |
src/HelixTool/.mcp/server.json |
packages[0].version |
"version": "0.8.0" |
Verify after editing:
grep -oP '(?<=<Version>)[^<]+' src/HelixTool/HelixTool.csproj
jq -r '.version, .packages[0].version' src/HelixTool/.mcp/server.json
All three must print the new version string.
Step 3 — Release notes
Write to .squad/release-notes/vX.Y.Z.md. Sections:
- Headline — one sentence describing the release theme.
- Highlights — top 3–5 bullets a user cares about.
- New Features — with PR citations (#NN).
- Bug Fixes — with PR citations.
- Dependencies — SDK bumps, security pins.
- Infrastructure — CI/tooling changes.
- Full Changelog —
https://github.com/lewing/helix.mcp/compare/vPREV...vNEXT
Step 4 — Build + test sanity check
dotnet build -c Release --no-incremental # must be: 0 Warning(s), 0 Error(s)
dotnet test -c Release --no-build # must be: 0 Failed
Stop and report if any tests are red. Do not proceed with a broken build.
Step 5 — Commit
git add -- src/HelixTool/HelixTool.csproj \
src/HelixTool/.mcp/server.json \
.squad/release-notes/vX.Y.Z.md
git commit -m "release: vX.Y.Z (version bump)
Co-authored-by: Copilot <[email protected]>"
git push -u origin release/vX.Y.Z
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.
- 7d ago First seen · 161 lines · 0 tokens per session scan A 84637588ed37
release-cut is a skill published in the GitHub repository lewing/helix.mcp (4 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,466 tokens. 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
Prepare and publish Perigon.CLI patch releases, including versioning, release notes, bilingual docs, validation, and the nuget-branch CI handoff.
watch-tag
Watch a GitHub repository for new tags using the gh-watch extension. Use when the user wants to be notified when a tag is created, when a release is cut, or when a tag that includes a specific commit appears (e.g. "tell me when my merge ships in a release").
changelog-writer
Use when a release is being prepared and a human-readable changelog must be generated from merged pull requests.
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.
versioning-policy
Semver versioning rules for Squad SDK and CLI — prevents prerelease version incidents.