agentmods.dev

release-management

release-management is a skill for Claude Code from yonatangross/orchestkit. It costs 58 tokens per session (1,448 once invoked), scanned A, original, MIT.

A release tool for GitHub, a service for hosting Git repositories and collaborating on code. It creates versions, changelogs, and releases from merged pull requests, with support for draft and prerelease workflows.

In plain words
What is it for?
Use it to choose a semantic version, generate a changelog, create a GitHub release, and verify the result through the command line.
Why use it?
It removes repetitive release steps and checks project version files before tagging, helping catch mismatched versions before publication.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: model in frontmatter; mentions Claude Code.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is gh release verify-asset v1.2.0 ./dist/app.zip.

Part of the ork plugin — 111 skills, 38 commands, 36 agents, 32 hooks shipped together

not rated 298repo +3 changed 22d ago A scan SkillSpector: warn 58 tokens original MIT

Good fit Use it to choose a semantic version, generate a changelog, create a GitHub release, and verify the result through the command line.

Compare 6 skills from other repositories ↓
View source ↗ yonatangross/orchestkit orchestkit.dev
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/yonatangross/orchestkit
agentmods
npx agentmods add skills/yonatangross/orchestkit/release-management

Made for: Claude Code.

Or install ork, the plugin that ships this one along with the rest of its 111 skills, 38 commands, 36 agents, 32 hooks.

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 release-management

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/yonatangross/orchestkit/release-management"><img src="https://agentmods.dev/badge/skills/yonatangross/orchestkit/release-management.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 58 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,448 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. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 1 finding, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium Excessive Agency · line 15
    Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.
    Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
How audits are shown
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.00058 $0.01448
Opus 5.5 $0.00023 $0.00579
Sonnet 5.5 $0.00012 $0.00290
Haiku 4.5 $0.00006 $0.00145

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

Security

Grade A, and why

release-management 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 22d ago.

The scan reads SKILL.md. This mod also ships 2 executable files (scripts/release-scripts.sh, scripts/version-manager.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.

plugins/ork/skills/release-management/SKILL.md · 192 lines

How it starts

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

Release Management

Automate releases with gh release, semantic versioning, and changelog generation.

CC ≥ 2.1.118 (M122): claude plugin tag <version> validates the plugin manifest hierarchy (marketplace.json, plugin.json, package.json, version.txt) before tagging. Runs --dry-run in CI before release-please opens its release PR; catches manifest drift early. See src/skills/chain-patterns/references/plugin-tag.md.

CRITICAL: Task Management is MANDATORY (CC 2.1.16)

BEFORE doing ANYTHING else, create tasks to track progress:

# 1. Create main task IMMEDIATELY
TaskCreate(
  subject="Release: {version}",
  description="Creating release with semantic versioning and changelog",
  activeForm="Releasing {version}"
)

# 2. Create subtasks for each release phase
TaskCreate(subject="Version & changelog", activeForm="Determining version and generating changelog")
TaskCreate(subject="Create release", activeForm="Creating GitHub release")
TaskCreate(subject="Verify & announce", activeForm="Verifying release and announcing")

# 3. Set dependencies for sequential phases
TaskUpdate(taskId="3", addBlockedBy=["2"])
TaskUpdate(taskId="4", addBlockedBy=["3"])

# 4. Update status as you progress
TaskUpdate(taskId="2", status="in_progress")  # When starting
TaskUpdate(taskId="2", status="completed")    # When done

Quick Reference

Create Release

# Auto-generate notes from PRs
gh release create v1.2.0 --generate-notes

# With custom title
gh release create v1.2.0 --title "Version 1.2.0: Performance Update" --generate-notes

# Draft release (review before publishing)
gh release create v1.2.0 --draft --generate-notes

# Pre-release (beta, rc)
gh release create v1.2.0-beta.1 --prerelease --generate-notes

# With custom notes
gh release create v1.2.0 --notes "## Highlights
- New auth system
- 50% faster search"

# From notes file
gh release create v1.2.0 --notes-file RELEASE_NOTES.md

List & View Releases

# List all releases
gh release list

# View specific release
gh release view v1.2.0

# View in browser
gh release view v1.2.0 --web

# JSON output
gh release list --json tagName,publishedAt,isPrerelease

Read the full file on GitHub · 192 lines

Files

What ships with it

11 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. 22d ago Changed · -9 lines 1f215d21cfa3
  2. 23d ago Changed · -1 lines b7b4c6d52a06
  3. 1mo ago Changed 0afdb3990b52
  4. 1mo ago Changed 3c79020e557e
  5. 1mo ago First seen · 202 lines · 58 tokens per session scan A 5c76202ea88d

Subscribe to this mod's changes

release-management is a skill published in the GitHub repository yonatangross/orchestkit (298 stars, last pushed today), licensed MIT. It adds 58 tokens to every session and 1,448 once invoked, about $0.0002 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-09-05.

Claude CodeGit and workflowLLMReleasesagentsai-developmentclaude-pluginlanggraph
Related

Other skills, from other repositories

changelog

Turn a range of commits or merged PRs into a changelog entry grouped by change type. Use when the user asks for release notes, a changelog, or "what changed" between two points.

omnigent-ai/omnigent · 44 tokens

otto-drive-pr

PR mergeability, CI, and live preview.

omnigent-ai/omnigent · 14 tokens

changelog

Update per-package CHANGELOG.md files for a Ratel release. Drafts entries with git-cliff (scoped per package), lets you curate, then writes the CHANGELOGs. Handles both RC entries and GA-graduation collapse (merging X.Y.Z-rc. sections into a single X.Y.Z section). Invoke before tagging a release.

ratel-ai/ratel · 74 tokens

jira-release

Assemble a release from a batch of Jira issues — one release branch, pull request, preview and tracking issue per repository — and, when a person says to ship it, merge it and move the cards on. Insert into the prompt of a run started on a batch of issues.

decocms/studio · 60 tokens

ship

Enter the Ship phase of CocoBrew. Reads review.md approval, generates structured commit, creates semantic version tag, optionally creates PR via gh CLI, and records deployment details. Requires approved review.

Snowflake-Labs/cocoplus · 41 tokens

playground-snapshot-release

Publish a Playground UI snapshot (@mastra/playground-ui and its workspace dependencies) from main or the current branch via the playground-snapshot mode of the Publish to npm workflow, wait for it to finish, then open a PR on mastra-ai/platform bumping the frontend to the published snapshot version. Use when asked to…

mastra-ai/mastra · 96 tokens