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/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.
<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="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.02708 |
| Opus 5.5 | $0.00031 | $0.01083 |
| Sonnet 5.5 | $0.00016 | $0.00542 |
| Haiku 4.5 | $0.00008 | $0.00271 |
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 8d 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 — 210 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 probe the required publishing credentials for
liveness — not mere presence — with
scripts/release/check-release-credentials.sh (read-only; never prints secret
values). Presence is not validity: MockServer 8.0.0 half-published because a
three-month-old npm token still existed (the old presence check passed) but
could no longer authenticate, so npm publish failed with 401 after the version
bumps had already been pushed. The probe calls each registry's own identity /
whoami / login-token endpoint and reports per-credential validity.
This same probe now also runs automatically as a hard gate in the release
preflight pipeline (.buildkite/release-preflight-pipeline.yml), on the
release queue — the only queue holding the mockserver-release/* grants, so
the only place website-role and the other release credentials can actually be
proven (dispatched via release-runner.sh check-credentials). That gate fails
the preflight build on any REJECTED / MALFORMED / ABSENT (exit 1) or
INDETERMINATE (exit 2) required credential, and is deliberately not soft_fail.
Running it by hand before you start a release is still worthwhile — it is the
fastest way to catch a dead or rotated credential without waiting for (or holding
up) a preflight build, and it works the same off-CI.
Version Recommendation Rules
Recommend the next release from the latest numeric mockserver-X.Y.Z tag, not from the current -SNAPSHOT alone.
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.
- 8d ago Changed · -3 lines 1ab2f8d2cae1
- 10d ago Changed · -2 lines 4f6e4ba86bf4
- 1mo ago Changed · +14 lines 21dfd1254899
- 1mo ago Changed · +45 lines 06f51006c830
- 1mo 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,999 stars, last pushed today), licensed Apache-2.0. It adds 78 tokens to every session and 2,708 once invoked, about $0.0003 per session on Opus 5.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
release
Fully automate a release with version-bump and childhood.
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.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.
updater_guide
Guidance for checking for and installing Row-Bot updates.
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".