agentmods.dev

release-management

release-management is a command for Claude Code from mock-server/mockserver-monorepo. It costs 75 tokens per session (1,116 once invoked), scanned A, original, Apache-2.0.

A release-preparation workflow for MockServer, a tool used to simulate HTTP services during software development and testing. It recommends a version and prepares the parameters for a Buildkite release pipeline.

In plain words
What is it for?
Use it to inspect the changelog, current development version, release configuration, documentation, and tags before preparing a MockServer release.
Why use it?
It reduces guesswork around whether a release is ready and which version should be published under Semantic Versioning rules.

Command for Claude Code

not rated 5.0k +4 yesterday A scan 75 tokens original Apache-2.0
View the source file mock-server/mockserver-monorepo
About the project

MockServer is a testing server and proxy that imitates APIs, records and changes network traffic, and deliberately introduces failures. It is for developers testing applications against unavailable dependencies, debugging requests, and checking how systems handle degraded services across several network protocols. The catalogue add-ons help operate, configure, and test MockServer.

mock-server/mockserver-monorepo · 4,964 stars · on GitHub

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/mock-server/mockserver-monorepo/release-management
Clone the repo
git clone --depth 1 https://github.com/mock-server/mockserver-monorepo

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

README.md
[![agentmods](https://agentmods.dev/badge/commands/mock-server/mockserver-monorepo/release-management.svg)](https://agentmods.dev/commands/mock-server/mockserver-monorepo/release-management)
Your own site
<a href="https://agentmods.dev/commands/mock-server/mockserver-monorepo/release-management"><img src="https://agentmods.dev/badge/commands/mock-server/mockserver-monorepo/release-management.svg" alt="Measured on agentmods" height="20"></a>
Per session 75 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,116 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 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.00075 $0.01116
Opus 5 $0.00037 $0.00558
Sonnet 5 $0.00015 $0.00223
Haiku 4.5 $0.00007 $0.00112

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

Security

Grade A, and why

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

.claude/commands/release-management.md · 118 lines

How it starts

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

Prepare a MockServer Release

Use this workflow before triggering the mockserver-release Buildkite pipeline.

Required Inputs

Inspect these sources every time:

  • changelog.md — especially the ## [Unreleased] section
  • mockserver/pom.xml — current development -SNAPSHOT version
  • .buildkite/release-pipeline.yml — supported release parameters and automated steps
  • docs/operations/release-process.md — operator-facing release guidance
  • Git tags matching mockserver-X.Y.Z — latest numeric release is the authoritative old-version

If AWS access is available, also verify the required secrets exist and contain the expected keys without printing secret values.

Version Recommendation Rules

Recommend the next release from the latest numeric mockserver-X.Y.Z tag, not from the current -SNAPSHOT alone.

Apply these rules in order:

  1. Major release — if any unreleased changelog bullet is explicitly marked BREAKING:
  2. Minor release — if there are meaningful bullets under Added or Changed and no BREAKING: markers
  3. Patch release — if there are only meaningful bullets under Fixed
  4. Block release — if the unreleased changelog is empty, vague, or not ready to publish

Definitions:

  • A "meaningful bullet" is a non-empty - ... entry
  • BREAKING: should appear at the start of an unreleased bullet when a major version bump is intended

Derived values:

  • release-version: recommended SemVer release
  • next-version: release-version patch increment plus -SNAPSHOT
  • old-version: latest numeric mockserver-X.Y.Z tag
  • release-type: full unless the user explicitly wants a partial rerun
  • create-versioned-site: yes for major or minor releases, no for patch releases

Readiness Checks

Validate each of these before declaring the release ready:

  1. changelog.md has meaningful unreleased bullets
  2. changelog.md does not already contain a section for the proposed release-version
  3. mockserver/pom.xml is currently on an X.Y.Z-SNAPSHOT version
  4. The pipeline supports the required outputs for this release:
    • Maven Central core artifacts
    • mockserver-maven-plugin
    • Docker Hub and AWS ECR Public images
    • mockserver-node
    • mockserver-client
    • Helm
    • Javadoc
    • SwaggerHub / OpenAPI
    • website
    • JSON Schema
    • PyPI
    • RubyGems
    • GitHub Release
  5. Required secrets are present:
    • mockserver-build/sonatype
    • mockserver-build/dockerhub
    • mockserver-build/pypi
    • mockserver-build/rubygems
    • mockserver-release/gpg-key
    • mockserver-release/github-token
    • mockserver-release/totp-seed
    • mockserver-release/npm-token
    • mockserver-release/swaggerhub
    • mockserver-release/website-role

Read the full file on GitHub · 118 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. 5d ago First seen · 118 lines · 75 tokens per session scan A 107a338acefa

Subscribe to this mod's changes

release-management is a command published in the GitHub repository mock-server/mockserver-monorepo (4,964 stars, last pushed yesterday), licensed Apache-2.0. It adds 75 tokens to every session and 1,116 once invoked, about $0.0004 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-30.

Git and workflowReleasesjava-clientjavascript-clientmock-servernode-clientnode-moduleproxy
Related

Other commands, from other repositories

Release Version

自动更新版本号、基于git日志生成修订日志、安装依赖、构建、打标签并发布到npm.

vtxf/mcp-all-in-one · 30 tokens

archive

name: OpenSpec: Archive description: Archive a deployed OpenSpec change and update specs. category: OpenSpec tags: [openspec, archive].

vtxf/mcp-all-in-one · 0 tokens

create-pr

Rebase from the latest origin/main, squash the commits from it, and then create a PR on github with intelligent commit messages based on staged changes. Invoke with /create-pr.

areal-project/AReaL · 40 tokens

push-and-release

Git pull, resolve conflicts, push, fix hook errors, then release.

nimbalyst/nimbalyst · 14 tokens

land

Cadence-tick autonomous PR babysitter (CI-fix, resolve, converge, merge, close, release).

gmickel/flow-next · 25 tokens

release

This compatibility command keeps /oh-my-claudecode:release available without loading the full release skill description in every Claude Code session.

Yeachan-Heo/oh-my-claudecode · 0 tokens