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/update-changelog/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/update-changelog)<a href="https://agentmods.dev/skills/contrast-security-oss/mcp-contrast/update-changelog"><img src="https://agentmods.dev/badge/skills/contrast-security-oss/mcp-contrast/update-changelog/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/contrast-security-oss/mcp-contrast/update-changelog"><img src="https://agentmods.dev/badge/skills/contrast-security-oss/mcp-contrast/update-changelog.svg" alt="Reviewed on agentmods" width="80" 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 Tool Misuse · line 139 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
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.00115 | $0.02521 |
| Opus 5 | $0.00057 | $0.01260 |
| Sonnet 5 | $0.00023 | $0.00504 |
| Haiku 4.5 | $0.00012 | $0.00252 |
Grade A, and why
update-changelog 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 12d 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 — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pre-release changelog update
Brings [Unreleased] in CHANGELOG.md up to date with every user-facing change merged
since the last release tag, so the release ships with a finished changelog. The skill
drafts, audits, and only then shows the human one final draft. Nothing is written to
disk before the human approves.
When to run. Before triggering the Gradle Release workflow (see RELEASING.md), or when a human explicitly asks. Not part of routine feature development.
Usage
/update-changelogruns the full flow./update-changelog <guidance>passes free-text hints, e.g./update-changelog the SBOM work is internal, skip it.- Deferred-landing mode, invoked by the
/releaseskill: draft, audit, and get the human's approval as usual, but skip the branch question in Step 1, all of Step 6, and Step 7. The range is the base range only. Return the approved draft text and the suggested next version to the caller, which creates the release branch and lands the changelog itself.
Ground rules
- Content goes into
[Unreleased]. Never stamp a version heading for the upcoming release. Version selection belongs to the release workflow, not this skill. - Versions that already have a changelog section are settled. Never reopen, rewrite, or re-audit them.
- Existing
[Unreleased]entries may be amended or expanded when they are incomplete or wrong. Never delete one silently. Propose deletions in the draft and let the human decide. - Report a suggested next version (breaking changes → major, new capabilities → minor,
otherwise patch). It is informational only. Do not act on it. Breaking here
means removed or renamed tools, or changes to hosting requirements, a new Java
version, a Spring Boot major, changed Docker or jar run instructions. Changes to
the
contrast-mcp-corelibrary API are not breaking on their own, its only consumer is internal. Small tool contract changes (parameters, response shape) stay minor, AI consumers adapt. - Do not create beads. This is a one-file docs change.
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.
- 12d ago First seen · 205 lines · 115 tokens per session scan A 726e1e2d25ec
update-changelog is a skill published in the GitHub repository Contrast-Security-OSS/mcp-contrast (23 stars, last pushed today), licensed Apache-2.0. It adds 115 tokens to every session and 2,521 once invoked, about $0.0006 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.