Borrowing it
Nothing to install: this file belongs to Contrast-Security-OSS/mcp-contrast. 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/Contrast-Security-OSS/mcp-contrast/main/.claude/skills/release/SKILL.mdgit clone --depth 1 https://github.com/Contrast-Security-OSS/mcp-contrastWrote 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/contrast-security-oss/mcp-contrast/release)<a href="https://agentmods.dev/skills/contrast-security-oss/mcp-contrast/release"><img src="https://agentmods.dev/badge/skills/contrast-security-oss/mcp-contrast/release.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Rogue Agent · line 178 Skill modifies its own code, configuration, or behavior at runtime. Self-modification enables an agent to escalate privileges, disable safety constraints, or install persistent backdoors.Fix: Prevent the skill from modifying its own code, SKILL.md, or configuration files. Treat skill files as read-only at runtime.
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.00106 | $0.02439 |
| Opus 5 | $0.00053 | $0.01220 |
| Sonnet 5 | $0.00021 | $0.00488 |
| Haiku 4.5 | $0.00011 | $0.00244 |
Grade A, and why
release scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
3. DockerHub: `curl -sf https://hub.docker.com/v2/repositories/contrast/mcp-contrast/tags/X.Y.Z`. How it starts
The opening of the file, as written. The whole thing — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release orchestration
Runs the whole release documented in RELEASING.md, composing /update-changelog and
/test-mcp-server. The flow is changelog-first: the audited changelog draft is the
evidence for the version decision, and the release ticket and branch are created only
after the human approves the version, so they are born with the right number.
Publishing to Artifactory and DockerHub is irreversible, so the human gates below are
mandatory, never skipped.
Usage
/release takes no arguments. The version always comes from the suggest-and-approve
gate in Phase 3.
Re-entry
Releases fail mid-flight more than anywhere else. On re-entry, detect completed work
from the repo and skip it: stamped changelog already on origin/main → go to Phase 5
or 6; release workflow already succeeded → go to Phase 7. The workflow itself is safe
to re-dispatch because it reuses an existing vX.Y.Z tag at HEAD.
Phase 1 — Preflight (read-only)
git fetch origin --tags -q. Confirm the working tree is clean and HEAD matchesorigin/main. If not, stop and tell the human.- Verify the
pr-toolsplugin is available (check for/pr-tools:create-prin the skill list). Phase 4 depends on it. If missing, stop and tell the human to install it per the CLAUDE.md "Required Plugins" section. - Confirm CI is green:
gh run list --branch main --workflow build.yml --limit 1 --json conclusion,headShaand check the run covers the currentorigin/mainHEAD. Red or stale CI stops the release by default. The human may explicitly override for a known-flaky failure, record the override in the final report. - Find the last release tag:
git tag --sort=-v:refname | grep -E '^v[0-9]+\.[0-9]+\.[0-9]+$' | head -1. - Enumerate the release content:
git log --oneline --merges vLAST..origin/main, plus the same without--mergesfor direct commits. If the range is empty, there is nothing to release, stop. - If every change in the range is internal (CI config, dependabot, refactors), ask the human whether to ship a dependency-bump release anyway. If yes, the Phase 2 draft must include a section summarizing the dependency updates (drawn from the dependabot PR titles, house style) so the stamped section is never empty.
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 First seen · 179 lines · 106 tokens per session scan A 88d6e9faf2fe
release is a skill published in the GitHub repository Contrast-Security-OSS/mcp-contrast (23 stars, last pushed 3d ago), licensed Apache-2.0. It adds 106 tokens to every session and 2,439 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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-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.
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
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.