Borrowing it
Nothing to install: this file belongs to davidruzicka/mcp4openapi. 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/davidruzicka/mcp4openapi/main/.claude/skills/prepare-release-publishing/SKILL.mdgit clone --depth 1 https://github.com/davidruzicka/mcp4openapiWrote 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/davidruzicka/mcp4openapi/prepare-release-publishing)<a href="https://agentmods.dev/skills/davidruzicka/mcp4openapi/prepare-release-publishing"><img src="https://agentmods.dev/badge/skills/davidruzicka/mcp4openapi/prepare-release-publishing/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/davidruzicka/mcp4openapi/prepare-release-publishing"><img src="https://agentmods.dev/badge/skills/davidruzicka/mcp4openapi/prepare-release-publishing.svg" alt="Reviewed on agentmods" width="80" 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.00076 | $0.00372 |
| Opus 5.5 | $0.00030 | $0.00149 |
| Sonnet 5.5 | $0.00015 | $0.00074 |
| Haiku 4.5 | $0.00008 | $0.00037 |
Grade A, and why
prepare-release-publishing 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 1mo 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.
What it actually says
Release Publishing
Run this skill from repository root.
Inputs
- Release part:
patch,minor, ormajor.
Procedure
- Run
./.claude/skills/prepare-release-publishing/scripts/prepare-release-publishing.sh <patch|minor|major>. - Confirm output reports:
- current version from
package.json - target version computed from
package.json - inserted
CHANGELOGheading in format## [x.y.z] - YYYY-MM-DD - successful
npm version <part> --no-git-tag-version - final consistency check passed
Guardrails
- Derive next version only from
package.json, never fromCHANGELOG.md. - Insert the release heading directly below
## [Unreleased]. - Keep existing
Unreleasednotes in place. - Fail if
CHANGELOG.mdhas no## [Unreleased]section. - Fail if computed target version and final
package.jsonversion differ. - Support
patch,minor, andmajoronly.
Command examples
./.claude/skills/prepare-release-publishing/scripts/prepare-release-publishing.sh patch
./.claude/skills/prepare-release-publishing/scripts/prepare-release-publishing.sh minor
./.claude/skills/prepare-release-publishing/scripts/prepare-release-publishing.sh major
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 36 lines · 76 tokens per session scan A f68fc16a0c11
prepare-release-publishing is a skill published in the GitHub repository davidruzicka/mcp4openapi (0 stars, last pushed 4d ago), licensed MIT. It adds 76 tokens to every session and 372 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-31.
Other skills, from other repositories
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.
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.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
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.