A release workflow for bundle-plugins, which package coding-agent add-ons together. It checks quality, security, documentation, tests, versions, and publishing readiness before distribution.

Use it when preparing a bundle-plugin release, synchronising versions, updating its changelog, publishing it, or checking whether it is ready.

It reduces the chance of releasing an inconsistent package with version drift, missing documentation, security problems, or broken installation.

releasing — Skill for Claude Code by OdradekAI

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 OdradekAI/bundles-forge --skill releasing

Clone the repo

git clone --depth 1 https://github.com/OdradekAI/bundles-forge

Made for: Claude Code.

Or install bundles-forge, the plugin that ships this one along with the rest of its 8 skills, 3 agents, 1 hook.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/odradekai/bundles-forge/releasing/github.svg)](https://agentmods.dev/skills/odradekai/bundles-forge/releasing)

Your own site

<a href="https://agentmods.dev/skills/odradekai/bundles-forge/releasing"><img src="https://agentmods.dev/badge/skills/odradekai/bundles-forge/releasing/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/odradekai/bundles-forge/releasing"><img src="https://agentmods.dev/badge/skills/odradekai/bundles-forge/releasing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 38 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,951 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.

Model	Per session	Once invoked
Fable 5.1	$0.00038	$0.02951
Opus 5	$0.00019	$0.01476
Sonnet 5	$0.00008	$0.00590
Haiku 4.5	$0.00004	$0.00295

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

Security

Grade A, and why

releasing 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 9d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/bump_version.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.

skills/releasing/SKILL.md · 267 lines

How it starts

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

Releasing Bundle-Plugins

Overview

Orchestrate the complete release workflow for a bundle-plugin: verify quality, scan for security risks, check documentation consistency, review change coherence, test locally, bump versions, update documentation, and publish to target platforms.

Core principle: Release is a checkpoint, not a formality. Every release deserves the full pipeline — even "minor" version bumps can introduce drift or break platform installs. Users should complete all agent, skill, and workflow development before invoking this skill.

Skill type: Rigid — follow every step exactly. Releases have no room for improvisation.

For version management infrastructure details (.version-bump.json schema, script usage, version setup for new projects), read references/version-infrastructure.md. For distribution strategy options, read references/distribution-strategy.md.

Announce at start: "I'm using the releasing skill to prepare this project for release."

Entry Detection

Context	Path
User wants to release a version, provides a project directory	Path 1: Standard release — run the full pipeline below
Urgent fix with small changes	Path 2: Hotfix release — run the abbreviated pipeline (see Hotfix Releases)
Project needs version infrastructure for the first time	Path 3: Version setup — read `references/version-infrastructure.md` § Version Setup

The Release Pipeline

0. Prerequisites  →  1. Pre-flight Checks  →  2. Address Findings
→  3. Change Review & Doc Sync  →  4. Local Testing
→  5. Version Bump  →  6. Release Notes
→  7. Final Verification  →  8. Publish

Step 0: Prerequisites

Verify all conditions before entering the pipeline. Hard requirements block the pipeline; soft requirements trigger warnings.

Hard requirements (must pass):

The project is a bundle-plugin (has skills/ directory and package.json)
Working tree is clean — git status shows no uncommitted or unstaged changes. All development work (agents, skills, workflows) must be committed before releasing.
The user knows the target version number (or wants help deciding)

Read the full file on GitHub · 267 lines

Files

What ships with it

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

9d ago First seen · 267 lines · 38 tokens per session scan A c94c9aeff4fb

Subscribe to this mod's changes

releasing is a skill published in the GitHub repository OdradekAI/bundles-forge (230 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 38 tokens to every session and 2,951 once invoked, about $0.0002 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.

Claude Code Git and workflow Releases agent-skills bundle-plugin claude-plugin claude-skills cursor-plugin

releasing

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Releasing Bundle-Plugins

Overview

Entry Detection

The Release Pipeline

Step 0: Prerequisites

What ships with it

What this file has done since we first saw it

Other skills, from other repositories

pdlc-ship

pdlc-changelog

changelog

changelog-rewrite-aggressively

release-update-downstream-packages

update-downstream-packages