Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/zakelfassi/skills-driven-development/release-cutnpx skills add zakelfassi/skills-driven-development --skill release-cutgit clone --depth 1 https://github.com/zakelfassi/skills-driven-developmentWrote 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/zakelfassi/skills-driven-development/release-cut)<a href="https://agentmods.dev/skills/zakelfassi/skills-driven-development/release-cut"><img src="https://agentmods.dev/badge/skills/zakelfassi/skills-driven-development/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 | $0.00070 | $0.00955 |
| Opus 5 | $0.00035 | $0.00477 |
| Sonnet 5 | $0.00014 | $0.00191 |
| Haiku 4.5 | $0.00007 | $0.00096 |
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 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Cut
Bump the version, generate a changelog, tag, and publish a GitHub release for shipctl.
Inputs
- Target version (semver, e.g.
1.2.0orpatch/minor/major) - Release channel (defaults to
stable;prefor release candidates) - Skip binary attach? (boolean, defaults to
false)
Steps
-
Verify the working tree is clean
git status --porcelainIf dirty, commit or stash before proceeding.
-
Run the full test suite
cargo test --workspaceAbort if any test fails.
-
Run the breaking-change audit (invoke the
breaking-change-auditskill) Confirms no accidental public-interface regressions before tagging. -
Bump the version
# For Rust: cargo set-version {version} # or edit Cargo.toml manually # For Go: # Update version constant in cmd/root.goCommit the version bump:
git commit -am "chore(release): bump version to {version}" -
Generate the changelog
scripts/release-cut.sh --changelog-only {version}Review
CHANGELOG.md— edit entries if the generated text is unclear. Commit:git commit -am "docs(changelog): {version} release notes" -
Create and push the tag
git tag -a "v{version}" -m "Release v{version}" git push origin "v{version}" -
Trigger cross-compile and attach binaries The CI matrix builds all registered target triples (see
cross-compile-matrixskill). Wait for thereleaseworkflow to complete:gh run watch --exit-status -
Draft the GitHub release
gh release create "v{version}" \ --title "v{version}" \ --notes-file CHANGELOG.md \ --draftReview the draft, then publish:
gh release edit "v{version}" --draft=false -
Announce (if applicable) Post in the team channel: title, key changes, install command:
cargo install shipctl --version {version}
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 First seen · 100 lines · 70 tokens per session scan A 791d307e3845
release-cut is a skill published in the GitHub repository zakelfassi/skills-driven-development (18 stars, last pushed 1mo ago), licensed MIT. It adds 70 tokens to every session and 955 once invoked, about $0.0003 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
finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup.
skillshare-changelog
Generate CHANGELOG.md entry from recent commits in conventional format. Also syncs the website changelog page. Use this skill whenever the user asks to: generate a changelog, document what changed between tags, or create a new CHANGELOG entry. If you see requests like "write the changelog for v0.17", "what changed…
skillshare-release
End-to-end release workflow for skillshare. Runs tests, generates changelog (via /changelog), optionally writes local RELEASENOTES, updates version numbers, commits, and drafts announcements. Use when the user says "release", "prepare release", "cut a release", "release v0.19", or any request to publish a new version.…
prepare-release
Prepare a new release by collecting commits, generating bilingual release notes, updating version files, and creating a release branch. Use when asked to prepare/create a release, bump version, or run /prepare-release.
comet-release
根据真实版本和分支范围准备 Comet 发布或发布说明更新,保持 Changelog 面向用户、双语网站文档一致、生成资产已验证,并明确 Git 交付边界。Beta、hotfix、版本检查、发布说明或发布就绪检查时使用。.
comet-safe-delivery
在保护无关脏改动、关联 worktree、子模块和用户明确边界的前提下,提交、推送、合并或完成范围明确的 Comet 变更。用户要求提交、推送、合并回目标分支、清理 worktree 或交付已准备好的改动时使用。.