agentmods.dev

MPNext: Command for Claude Code

.claude/commands/release.md

release is a command for Claude Code from MinistryPlatform-Community/MPNext. It costs 0 tokens per session (1,516 once invoked), scanned A, original, MIT.

A command for creating a GitHub release, which is a published version of a project stored on GitHub. It generates the release notes from pull requests that have been merged.

In plain words
What is it for?
Use it when publishing a new GitHub version after changes have been merged.
Why use it?
It removes the need to collect merged changes and write the release summary by hand. The release is based on the project's completed pull requests.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

This is MinistryPlatform-Community/MPNext's own configuration. It tells Claude Code how to work on MPNext 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 MPNext configures →

not rated 14repo +1 changed 28d ago A scan 0 tokens original MIT
View source ↗ MinistryPlatform-Community/MPNext
Reuse

Borrowing it

Nothing to install: this file belongs to MinistryPlatform-Community/MPNext. 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/MinistryPlatform-Community/MPNext/main/.claude/commands/release.md
Clone the repo
git clone --depth 1 https://github.com/MinistryPlatform-Community/MPNext

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/ministryplatform-community/mpnext/release/github.svg)](https://agentmods.dev/commands/ministryplatform-community/mpnext/release)
Your own site
<a href="https://agentmods.dev/commands/ministryplatform-community/mpnext/release"><img src="https://agentmods.dev/badge/commands/ministryplatform-community/mpnext/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/ministryplatform-community/mpnext/release"><img src="https://agentmods.dev/badge/commands/ministryplatform-community/mpnext/release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 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,516 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.00000 $0.01516
Opus 5.5 $0.00000 $0.00606
Sonnet 5.5 $0.00000 $0.00303
Haiku 4.5 $0.00000 $0.00152

Measured 28d ago against content hash 8794397a0038, 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 28d 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 · 140 lines

How it starts

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

Release Command

Create a GitHub release with auto-generated release notes from merged pull requests.

Instructions

  1. Gather context:

    • Run gh release list --limit 5 to find the most recent release (if any)
    • Run git tag --sort=-version:refname | head -5 to see existing tags
    • If a previous release exists, identify its tag to scope the changelog
    • Run git log --oneline (from last release tag to HEAD, or recent commits if first release) to understand what's new

  2. Identify PRs to include:

    • If this is the first release, run gh pr list --state merged --limit 20 --json number,title,mergedAt,body,labels to get recent merged PRs
    • If a previous release exists, find PRs merged since that release using gh pr list --state merged --search "merged:>YYYY-MM-DD" --json number,title,mergedAt,body,labels
    • Present the list of PRs to the user and ask which to include (default: all)

  3. Determine version:

    • Auto-compute the version tag using calver format: v{YYYY}.{MM}.{DD}.{HHmm} based on the current date and time
    • Generate it with: date -u +v%Y.%m.%d.%H%M (UTC time)
    • Example: v2026.02.20.1735 means 2026-02-20 at 17:35 UTC
    • Show the computed version to the user for confirmation
    • If --tag argument was provided, use that instead of auto-computing
    • If the computed tag already exists, append a .1 suffix (e.g., v2026.02.20.1735.1)

  4. Generate release notes:

    • Categorize included PRs by type using PR title prefixes and content:
      • ⚠️ Breaking Changes — any PR with breaking changes (migration steps, renamed APIs, changed URLs, removed features)
      • 🚀 Features — PRs with feat: prefix or feature work
      • 🐛 Bug Fixes — PRs with fix: prefix or bug fixes
      • 📚 Documentation — PRs with docs: prefix or doc-only changes
      • 🔧 Maintenance — dependency updates, refactoring, CI changes, chores
    • For each PR, write a concise summary line: **Short title** (#number) — One-sentence description.
    • Pull the description from the PR body's Summary section if available
    • Only include categories that have PRs in them
    • Ask the user if there are any breaking changes or additional notes to add

Read the full file on GitHub · 140 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. 28d ago Changed · +2 lines 8794397a0038
  2. 1mo ago First seen · 138 lines · 0 tokens per session scan A fb8c37e7bb81

Subscribe to this mod's changes

release is a command published in the GitHub repository MinistryPlatform-Community/MPNext (14 stars, last pushed 7d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,516 tokens. 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.

Git and workflowReleases
Related

Other commands, from other repositories

land

Resolve and squash merge one named, currently authorized pull request.

gmickel/flow-next · 13 tokens

quality

A command for temporarily clearing a release quality gate or one named check, while recording the reason and expiry time. A quality gate is a required check that normally blocks completion or release.

Desko77/claude-code-skills-1c · 18 tokens

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.

OpenHands/extensions · 44 tokens

release-plan

A release-planning command for a software change. It documents the release scope, rollback plan, gradual or full rollout, and monitoring before waiting for human approval.

alisunstar/OpenSunstar · 0 tokens

release-manager

Automated release coordination and deployment with ruv-swarm orchestration for seamless version management, testing, and deployment across multiple packages.

ruvnet/agentic-flow · 0 tokens

rally-merge-pr

You are merging the current branch's PR and syncing the feature branch with main. Follow each step exactly.

ddgonzal3/rally · 0 tokens