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.
npx agentmods add commands/c0ntr0lledcha0s/claude-code-plugin-automations/release-preparegit clone --depth 1 https://github.com/C0ntr0lledCha0s/claude-code-plugin-automationsWrote 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.
[](https://agentmods.dev/commands/c0ntr0lledcha0s/claude-code-plugin-automations/release-prepare)<a href="https://agentmods.dev/commands/c0ntr0lledcha0s/claude-code-plugin-automations/release-prepare"><img src="https://agentmods.dev/badge/commands/c0ntr0lledcha0s/claude-code-plugin-automations/release-prepare.svg" alt="Measured on agentmods" height="20"></a>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.00014 | $0.01221 |
| Opus 5 | $0.00007 | $0.00611 |
| Sonnet 5 | $0.00003 | $0.00244 |
| Haiku 4.5 | $0.00001 | $0.00122 |
Grade A, and why
release-prepare 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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 207 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prepare Release
Analyzes commits since the last release and prepares all release artifacts.
Usage
/release-prepare auto # Auto-detect version from commits
/release-prepare minor # Force minor version bump
/release-prepare major # Force major version bump
/release-prepare patch # Force patch version bump
What This Does
- Analyze Commits: Get all commits since last release tag
- Determine Version: Calculate version bump based on commit types
- Generate Changelog: Create changelog entries grouped by type
- Create Release Notes: Generate comprehensive release notes
- Prepare Files: Show what version files need updating
Workflow
Step 1: Get Last Release
Find the most recent release tag and analyze commits since then:
# Get last release tag
LAST_TAG=$(git describe --tags --abbrev=0 2>/dev/null || echo "")
echo "Last release: ${LAST_TAG:-'No previous release'}"
# Count commits since last release
if [ -n "$LAST_TAG" ]; then
COMMIT_COUNT=$(git rev-list --count $LAST_TAG..HEAD)
else
COMMIT_COUNT=$(git rev-list --count HEAD)
fi
echo "Commits since last release: $COMMIT_COUNT"
Step 2: Analyze Commit Types
Parse commits using conventional commit format:
# Get commits since last tag
if [ -n "$LAST_TAG" ]; then
COMMITS=$(git log $LAST_TAG..HEAD --pretty=format:"%s")
else
COMMITS=$(git log --pretty=format:"%s")
fi
# Count by type
FEAT_COUNT=$(echo "$COMMITS" | grep -c "^feat" || echo "0")
FIX_COUNT=$(echo "$COMMITS" | grep -c "^fix" || echo "0")
BREAKING_COUNT=$(echo "$COMMITS" | grep -c "!" || echo "0")
BREAKING_FOOTER=$(echo "$COMMITS" | grep -c "BREAKING CHANGE" || echo "0")
echo "Features: $FEAT_COUNT"
echo "Fixes: $FIX_COUNT"
echo "Breaking changes: $((BREAKING_COUNT + BREAKING_FOOTER))"
Step 3: Determine Version Bump
Based on argument or auto-detection:
Auto-detection logic:
- Any breaking changes (
!orBREAKING CHANGE) → MAJOR - Any features (
feat:) → MINOR - Only fixes/docs/chores → PATCH
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.
- 6d ago First seen · 207 lines · 14 tokens per session scan A 555ef39007d7
release-prepare is a command published in the GitHub repository C0ntr0lledCha0s/claude-code-plugin-automations (3 stars, last pushed 6mo ago), licensed MIT. It adds 14 tokens to every session and 1,221 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.
Other commands, from other repositories
push-and-release
Git pull, resolve conflicts, push, fix hook errors, then release.
land
Cadence-tick autonomous PR babysitter (CI-fix, resolve, converge, merge, close, release).
release
Create a release branch, run changeset version, review changelog, and prepare PR.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
release
Walk the llmwiki release process step by step.
ship
Ship is the operational release-prep flow for a connected project repo.