agentmods.dev

cut-release

cut-release is a skill for Claude Code, Codex from TheSmuks/ai-project-template. It costs 22 tokens per session (1,479 once invoked), scanned A, original, MIT.

A release procedure that chooses a semantic version, updates project version files and the changelog, and publishes a GitHub release. Semantic versioning uses major, minor, and patch numbers to describe breaking changes and regular updates.

In plain words
What is it for?
Use it after changes are ready to release. It can determine the next version from commit types, ask for confirmation, create a commit and pull request, merge it, and publish the release.
Why use it?
It gathers release preparation into one repeatable process and prevents versions, change notes, and the published release from getting out of sync.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions AGENTS.md.

not rated 7repo +1 4mo ago A scan 22 tokens original MIT

Good fit Use it after changes are ready to release. It can determine the next version from commit types, ask for confirmation, create a commit and pull request, merge it, and publish the release.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/thesmuks/ai-project-template/cut-release
View source ↗ TheSmuks/ai-project-template
Install

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.

Any agent
npx skills add TheSmuks/ai-project-template --skill cut-release
Clone the repo
git clone --depth 1 https://github.com/TheSmuks/ai-project-template

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for cut-release

README.md
[![agentmods](https://agentmods.dev/badge/skills/thesmuks/ai-project-template/cut-release/github.svg)](https://agentmods.dev/skills/thesmuks/ai-project-template/cut-release)
Your own site
<a href="https://agentmods.dev/skills/thesmuks/ai-project-template/cut-release"><img src="https://agentmods.dev/badge/skills/thesmuks/ai-project-template/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.

agentmods 80×15 button for cut-release

Your own site · 80×15
<a href="https://agentmods.dev/skills/thesmuks/ai-project-template/cut-release"><img src="https://agentmods.dev/badge/skills/thesmuks/ai-project-template/cut-release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 22 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,479 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00022 $0.01479
Opus 5 $0.00011 $0.00740
Sonnet 5 $0.00004 $0.00296
Haiku 4.5 $0.00002 $0.00148

Measured 10d ago against content hash 387203631793, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

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.

The scan reads SKILL.md. This mod also ships 2 executable files (scripts/cut-release.sh, scripts/update_changelog.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

.omp/skills/cut-release/SKILL.md · 197 lines

How it starts

The opening of the file, as written. The whole thing — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Cut Release

Automated release workflow: determine version → delegate to cut-release.sh → commit → create PR → merge → publish GitHub release.

When to Use

Invoke this skill whenever you are ready to cut a new release. Common triggers:

  • After merging feature branches that warrant a version bump
  • Before publishing a new skill or template version
  • When [Unreleased] in CHANGELOG.md has accumulated changes worth releasing

Prerequisites

  • All work for this release is committed and pushed
  • CHANGELOG.md has entries under [Unreleased]
  • You have push access to the repository

Phase 1: Determine Version (You do this)

  1. Read current version from .template-version:

    cat .template-version

  2. Read changelog to understand what has changed under [Unreleased]:

    head -30 CHANGELOG.md

  3. Compute next version using semver:

    • feat: commits → minor bump (e.g. 1.2.0 → 1.3.0)
    • fix: commits → patch bump (e.g. 1.2.0 → 1.2.1)
    • feat!: or BREAKING CHANGE in body → major bump (e.g. 1.2.0 → 2.0.0)

  4. Ask user to confirm or override the computed version before proceeding.

If [Unreleased] is empty, abort — nothing to release.

Phase 2: Execute Release (cut-release.sh does this)

Run the automation script with the version bump:

bash .omp/skills/cut-release/scripts/cut-release.sh <OLD_VERSION> <NEW_VERSION>

Example:

bash .omp/skills/cut-release/scripts/cut-release.sh 0.5.0 0.6.0

What the script does:

  1. Pre-flight: Verifies OLD_VERSION exists in all 7 version manifest files. Aborts if any are missing (prevents wrong version being passed).
  2. Update files: Replaces version in all manifest files:
    File Pattern
    .template-version whole file content
    README.md template-vX.Y.Z in badge
    AGENTS.md version **X.Y.Z**
    SETUP_GUIDE.md `X.Y.Z`
    .omp/skills/template-guide/SKILL.md (X.Y.Z) in examples

.omp/skills/template-guide/scripts/audit.sh | TEMPLATE_VERSION=X.Y.Z line | | CHANGELOG.md | Creates new version section from Unreleased |

Read the full file on GitHub · 197 lines

Files

What ships with it

2 files 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.

Changes

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.

  1. 10d ago First seen · 197 lines · 22 tokens per session scan A 387203631793

Subscribe to this mod's changes

cut-release is a skill published in the GitHub repository TheSmuks/ai-project-template (7 stars, last pushed 4mo ago), licensed MIT. It adds 22 tokens to every session and 1,479 once invoked, about $0.0001 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-31.

Git and workflowReleasesagents-mdaiautomationbest-practicesboilerplatecode-qualityreleasesemverversioningworkflow
Related

Other skills, from other repositories

cargo-release

PM-invocable protocol for Cargo publish and release operations in the trusty-tools Rust monorepo: semver rules, 10-step release sequence, macOS codesign safety, and cross-crate dependency ordering.

bobmatnyc/claude-mpm-skills · 45 tokens

github-release-management

Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.

ruvnet/agentic-flow · 27 tokens

Release Engineering

Semantic versioning, changelog generation, and release/hotfix management so releases are predictable and reversible.

niels-emmer/myace · 24 tokens

release-deploy

Release and deploy via GitHub tags and GitHub Actions (not every commit). Creates production releases from main and beta releases from staging using the GitHub CLI. Use when the user asks to release, ship, deploy, cut a version, tag a release, publish beta/production, create a GitHub Release, or bump a semver tag. On…

afaraha8403/balakit · 94 tokens

github-release-management

Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.

proffesor-for-testing/agentic-qe · 27 tokens

github-release-management

Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.

ruvnet/ruv-FANN · 27 tokens