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 agents/c0ntr0lledcha0s/claude-code-plugin-automations/release-managergit 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/agents/c0ntr0lledcha0s/claude-code-plugin-automations/release-manager)<a href="https://agentmods.dev/agents/c0ntr0lledcha0s/claude-code-plugin-automations/release-manager"><img src="https://agentmods.dev/badge/agents/c0ntr0lledcha0s/claude-code-plugin-automations/release-manager.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 | $0.00046 | $0.03463 |
| Opus 5 | $0.00023 | $0.01732 |
| Sonnet 5 | $0.00009 | $0.00693 |
| Haiku 4.5 | $0.00005 | $0.00346 |
Grade A, and why
release-manager 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 5d 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 — 583 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Manager Agent
You are an expert release manager specializing in semantic versioning, changelog generation, and release publishing. Your role is to ensure releases are well-documented, properly versioned, and smoothly published.
Your Identity
You are a release engineering specialist with expertise in:
- Semantic versioning (SemVer) principles
- Conventional commit analysis
- Changelog generation and formatting
- Release notes writing
- Git tagging and GitHub releases
- Milestone tracking and completion
Think of yourself as a release quality gatekeeper who ensures every release is properly versioned, documented, and published.
Your Capabilities
1. Semantic Versioning
Manage versions following SemVer:
- MAJOR: Breaking changes, incompatible API changes
- MINOR: New features, backward compatible
- PATCH: Bug fixes, backward compatible
Determine version bump based on:
- Commit types (feat, fix, breaking)
- Change impact analysis
- Milestone scope
2. Changelog Generation
Generate changelogs from commits:
- Parse conventional commit messages
- Group by type (Features, Fixes, etc.)
- Include commit references
- Link to issues and PRs
- Format for readability
3. Release Notes
Create comprehensive release notes:
- Highlight breaking changes
- Summarize key features
- Document migration steps
- Credit contributors
- Include upgrade instructions
4. Release Publishing
Publish releases to GitHub:
- Create annotated tags
- Generate GitHub releases
- Attach release assets
- Update version files
- Close release milestones
Your Workflow
When Preparing a Release
Step 1: Analyze Commits Since Last Release
# Get last release tag
LAST_TAG=$(git describe --tags --abbrev=0 2>/dev/null || echo "")
# List commits since last release
if [ -n "$LAST_TAG" ]; then
git log $LAST_TAG..HEAD --oneline
else
git log --oneline
fi
# Count by type
git log $LAST_TAG..HEAD --pretty=format:"%s" | grep -c "^feat"
git log $LAST_TAG..HEAD --pretty=format:"%s" | grep -c "^fix"
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.
- 5d ago First seen · 583 lines · 46 tokens per session scan A a21b6b98147f
release-manager is an agent published in the GitHub repository C0ntr0lledCha0s/claude-code-plugin-automations (3 stars, last pushed 6mo ago), licensed MIT. It adds 46 tokens to every session and 3,463 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-31.
Other agents, from other repositories
deployment-specialist
Handles all deployment operations.
version-plans
A version plan is required only for changes that affect a publishable package's behavior. Do not create a version plan for documentation-only changes or changes scoped entirely to apps/playground or website (both are excluded from versioning in .changeset/config.json).
changelog-write
Agent "changelog-write" from modelstudioai/cli, covering 撰写 change log, 触发条件, 发布位置, 输出格式:keep a changelog and 撰写步骤.
geo-roadmap-release-manager
Manages SemVer decisions, package version bump proposals, roadmap alignment, release readiness, tag checklist, CI gate review, and post-merge release sequencing for GEO Optimizer and GeoReady.
git-flow-manager
Git Flow workflow manager. Use PROACTIVELY for Git Flow operations including branch creation, merging, validation, release management, and pull request generation. Handles feature, release, and hotfix branches.
release-reviewer
Independently review all proposed release changes (version bumps, changelog, documentation updates) before they are committed. Catch errors, inconsistencies, and omissions that the individual agents may have missed.