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.
Borrowing it
Nothing to install: this file belongs to mock-server/mockserver-monorepo. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/mock-server/mockserver-monorepo/master/.opencode/skills/release-management/SKILL.mdgit clone --depth 1 https://github.com/mock-server/mockserver-monorepoWrote 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/skills/mock-server/mockserver-monorepo/release-management)<a href="https://agentmods.dev/skills/mock-server/mockserver-monorepo/release-management"><img src="https://agentmods.dev/badge/skills/mock-server/mockserver-monorepo/release-management.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.00078 | $0.01674 |
| Opus 5 | $0.00039 | $0.00837 |
| Sonnet 5 | $0.00016 | $0.00335 |
| Haiku 4.5 | $0.00008 | $0.00167 |
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 7d 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 — 156 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]sectionmockserver/pom.xml— current development-SNAPSHOTversion.buildkite/release-pipeline.yml— supported release parameters and automated stepsdocs/operations/release-process.md— operator-facing release guidance- Git tags matching
mockserver-X.Y.Z— latest numeric release is the authoritativeold-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:
- Major release — if any unreleased changelog bullet is explicitly marked
BREAKING: - Minor release — if there are meaningful bullets under
AddedorChangedand noBREAKING:markers - Patch release — if there are only meaningful bullets under
Fixed - 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 releasenext-version:release-versionpatch increment plus-SNAPSHOTold-version: latest numericmockserver-X.Y.Ztagrelease-type:fullunless the user explicitly wants a partial reruncreate-versioned-site:yesfor major or minor releases,nofor patch releases
Readiness Checks
Validate each of these before declaring the release ready:
changelog.mdhas meaningful unreleased bulletschangelog.mddoes not already contain a section for the proposedrelease-versionmockserver/pom.xmlis currently on anX.Y.Z-SNAPSHOTversion- The pipeline supports the required outputs for this release:
- Maven Central core artifacts
mockserver-maven-plugin- Docker Hub and AWS ECR Public images
mockserver-nodemockserver-client- Helm
- Javadoc
- SwaggerHub / OpenAPI
- website
- JSON Schema
- PyPI
- RubyGems
- GitHub Release
- Required secrets are present:
mockserver-build/sonatypemockserver-build/dockerhubmockserver-build/pypimockserver-build/rubygemsmockserver-release/gpg-keymockserver-release/github-tokenmockserver-release/totp-seedmockserver-release/npm-tokenmockserver-release/swaggerhubmockserver-release/website-role
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.
- 7d ago First seen · 156 lines · 78 tokens per session scan A 1352990589ab
release-management is a skill published in the GitHub repository mock-server/mockserver-monorepo (4,965 stars, last pushed yesterday), licensed Apache-2.0. It adds 78 tokens to every session and 1,674 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.
Other skills, from other repositories
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
updater_guide
Guidance for checking for and installing Row-Bot updates.