mulch: Command for Claude Code

.claude/commands/release.md

release is a command for Claude Code from jayminwest/mulch. It costs 1 tokens per session (958 once invoked), scanned A, original, MIT.

A release-preparation command for a software project. It reviews changes since the previous version, runs tests, updates the version number, and adds a categorized changelog entry.

In plain words
What is it for?
Use it before publishing a major, minor, or patch release to update project documentation and version records.
Why use it?
It gathers the routine release work into one documented process and helps keep version information and release notes aligned.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution. Also seen: mentions CLAUDE.md.

This is jayminwest/mulch's own configuration. It tells Claude Code how to work on mulch itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything mulch configures →

Reuse

Borrowing it

Nothing to install: this file belongs to jayminwest/mulch. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/jayminwest/mulch/main/.claude/commands/release.md
Clone the repo
git clone --depth 1 https://github.com/jayminwest/mulch

Made for: Claude Code.

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

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

Your own site · 80×15
<a href="https://agentmods.dev/commands/jayminwest/mulch/release"><img src="https://agentmods.dev/badge/commands/jayminwest/mulch/release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 958 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.00001 $0.00958
Opus 5.5 $0.00000 $0.00383
Sonnet 5.5 $0.00000 $0.00192
Haiku 4.5 $0.00000 $0.00096

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

Security

Grade A, and why

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

.claude/commands/release.md · 90 lines

How it starts

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

intro

Prepare a release by updating docs and bumping the version.

User specified: $ARGUMENTS

Steps

1. Analyze changes since last release

  • Run git log --oneline to find the last version tag/release commit
  • Run git diff --stat <last-release>..HEAD to see all changed files
  • Read the commit messages to understand what was added, fixed, and changed
  • Run npm test to get the current test count, file count, and expect() count

2. Determine version bump

  • If the user specified major, minor, or patch above, use that
  • Default: patch if nothing was specified
  • Current version is in package.json ("version" field) and src/cli.ts (.version() call)

3. Bump version

Run: bun run version:bump <major|minor|patch>

This atomically updates both package.json and src/cli.ts.

4. Update CHANGELOG.md

  • Add a new ## [X.Y.Z] - YYYY-MM-DD section under ## [Unreleased]
  • Categorize changes into ### Added, ### Fixed, ### Changed subsections
  • Use sub-headers (####) for grouping related changes (e.g., "New CLI Commands", "Testing")
  • Include updated test counts (tests, files, expect() calls)
  • Update the comparison links at the bottom of the file:
    • [Unreleased] link should compare against the new version
    • Add a new link for the new version comparing against the previous

5. Update CLAUDE.md

  • Update command counts if new commands were added
  • Add new files to the directory structure listing
  • Update any descriptions that changed (e.g., file format migrations)
  • Keep the structure consistent with existing entries

6. Update README.md

  • Update test counts in the Tech Stack and Development sections
  • Update command counts in the Project Structure section
  • Add new CLI commands/flags to the CLI Reference section
  • Update architecture descriptions if features changed
  • Add new files to the Project Structure listing

7. Update CONFIG.md

CONFIG.md is the user-facing reference for every configuration surface Mulch exposes (the .mulch/mulch.config.yaml schema, hooks, custom types, decay, recipes, CLI flags). Releases that touch any of these MUST update it; if nothing relevant changed, say so explicitly in the summary so it's a deliberate choice, not an oversight.

Read the full file on GitHub · 90 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. 1mo ago First seen · 90 lines · 1 tokens per session scan A 3ab22b983bdf

Subscribe to this mod's changes

release is a command published in the GitHub repository jayminwest/mulch (337 stars, last pushed 25d ago), licensed MIT. It adds 1 tokens to every session and 958 once invoked, about $0.0000 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.