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 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/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/zakelfassi/skills-driven-development/release-cut"><img src="https://agentmods.dev/badge/skills/zakelfassi/skills-driven-development/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.00070 | $0.00955 |
| Opus 5.5 | $0.00028 | $0.00382 |
| Sonnet 5.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 1mo 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.
- 1mo 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 3mo ago), licensed MIT. It adds 70 tokens to every session and 955 once invoked, about $0.0003 per session on Opus 5.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
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, splitting uncommitted work in a messy working tree into clean atomic commits, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple…
comet-archive
A workflow for the fifth stage of Comet Classic: archiving a completed change, merging its specification updates, and finishing the branch. It uses Comet commands and a fixed layout for tracking the change.
finishing-a-development-branch
A process for finishing a completed development branch. A branch is a separate line of code changes that can later be merged or submitted as a pull request.
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
Prepare and review skillshare releases using the Release Please PR, verify the proposed version and changelog, inspect draft assets, and publish through the manual Publish Release workflow when explicitly authorized. Use when the user says "release", "prepare release", "cut a release", or asks to publish a new…
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.