release

A release procedure for publishing a new version of a project on GitHub, a platform for hosting and collaborating on code.

In plain words
What is it for?
Use it to prepare and trigger a GitHub release with automated notes, including draft or prerelease options.
Why use it?
It checks important release conditions, such as the branch, working tree, changelog, version format, and existing tags, before starting the release workflow.

Command for Claude Code

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.

agentmods
npx agentmods add commands/alirezarezvani/claudeforge/release
Clone the repo
git clone --depth 1 https://github.com/alirezarezvani/ClaudeForge

Made for: Claude Code.

Per session 7 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,296 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 2 findings. Scan, not verified.
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 $0.00007 $0.01296
Opus 5 $0.00003 $0.00648
Sonnet 5 $0.00001 $0.00259
Haiku 4.5 $0.00001 $0.00130

Measured 2d ago against content hash 3485bb27e240, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade C, and why

release scanned grade C with 2 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 2d 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.

Downloads and executes remote codehighSupply chain

curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.

curl -fsSL https://raw.githubusercontent.com/alirezarezvani/ClaudeForge/main/install.sh | bash

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -fsSL https://raw.githubusercontent.com/alirezarezvani/ClaudeForge/main/install.sh | bash
.claude/commands/github/release.md · 222 lines

How it starts

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

Create GitHub Release

You are helping the user create a GitHub release for ClaudeForge.

Prerequisites Check

  1. Verify on main branch

    git branch --show-current
    
    • Should be main
    • If not, git checkout main && git pull
  2. Check for uncommitted changes

    git status
    
    • Should be clean
  3. Verify CHANGELOG.md updated

    grep -A 10 "## \[" CHANGELOG.md | head -15
    
    • Should have entry for new version

Workflow

  1. Determine Version

    • Ask user for version number
    • Validate semantic versioning format (X.Y.Z)
    • Examples: 1.1.0, 1.0.1, 2.0.0-beta.1
  2. Check Tag Doesn't Exist

    git tag -l "v1.1.0"
    
    • Should return nothing
    • If tag exists, ask user to choose different version
  3. Verify CHANGELOG.md

    • Check if version is documented
    • Extract release notes for this version
    • Show preview to user
  4. Run Release Workflow

    Option 1: Via GitHub CLI

    gh workflow run release.yml \
      -f version=1.1.0 \
      -f prerelease=false \
      -f draft=false
    

    Option 2: Via GitHub UI

    • Go to Actions → Create Release
    • Click "Run workflow"
    • Enter version: 1.1.0
    • Select options (prerelease, draft)
    • Click "Run workflow"
  5. Monitor Workflow

    gh run list --workflow=release.yml --limit 1
    gh run watch
    
  6. Verify Release Created

    gh release list
    gh release view v1.1.0
    

Release Types

Stable Release:

  • Version: X.Y.Z (e.g., 1.1.0)
  • Prerelease: false
  • Draft: false
  • Published immediately

Pre-Release:

  • Version: X.Y.Z-beta.N (e.g., 1.2.0-beta.1)
  • Prerelease: true
  • Draft: false
  • Marked as pre-release on GitHub

Draft Release:

  • Version: X.Y.Z
  • Draft: true
  • Not published until manually approved

Release Notes Generation

The release workflow automatically:

  1. Extracts notes from CHANGELOG.md
  2. Adds installation instructions
  3. Lists commits since last release
  4. Includes full changelog link

Read the full file on GitHub · 222 lines

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. 2d ago First seen · 222 lines · 7 tokens per session scan C 3485bb27e240

Subscribe to this mod's changes

release is a command published in the GitHub repository alirezarezvani/ClaudeForge (422 stars, last pushed 3mo ago), licensed MIT. It adds 7 tokens to every session and 1,296 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.