Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/samanhappy/mcphub/release-notesnpx skills add samanhappy/mcphub --skill release-notesgit clone --depth 1 https://github.com/samanhappy/mcphubWrote 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/samanhappy/mcphub/release-notes)<a href="https://agentmods.dev/skills/samanhappy/mcphub/release-notes"><img src="https://agentmods.dev/badge/skills/samanhappy/mcphub/release-notes.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 | $0.00058 | $0.01373 |
| Opus 5 | $0.00029 | $0.00687 |
| Sonnet 5 | $0.00012 | $0.00275 |
| Haiku 4.5 | $0.00006 | $0.00137 |
Grade A, and why
release-notes 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 4d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- release-notes — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Notes
Rewrite an existing GitHub release's body into the project's bilingual template, then push it back. The repo's release pipeline auto-generates a raw body on tag push (generate_release_notes: true) that does not match the bilingual template — this skill cleans it up.
Required structure
Every release body must follow this section order. Optional sections are omitted entirely when they have no content — never leave an empty section, never use None/无 placeholders.
| Section | Required | Chinese pair |
|---|---|---|
## Summary |
yes (non-empty) | — |
## Features |
optional | ## 功能 |
## Fixes |
optional | ## 修复 |
## Breaking Changes |
optional | ## 破坏性变更 |
## 摘要 |
yes (non-empty) | pair of Summary |
## New Contributors |
optional (English only, no Chinese pair) | — |
## References |
yes (non-empty) | — |
Rules enforced by scripts/validate-release-notes.js (CI runs it on publish/edit):
Summary,摘要,Referencesmust be present and non-empty.- Each optional English section and its Chinese pair must appear together — having one without the other fails validation.
- Optional sections with no real content are omitted, not stubbed.
Workflow
-
Resolve the target release.
- If the user gave a tag (e.g.
v1.0.14), use it. - Otherwise use the latest:
gh release list --limit 1.
- If the user gave a tag (e.g.
-
Fetch the existing body.
gh release view <tag> --json body -q .body- Read it to find an existing
Full changelog: ...compare/<prev>...<tag>line to learn the previous tag. Also note any PR list already present, but do not trust it blindly — re-fetch authoritatively in step 4.
-
Resolve the previous tag (the compare range).
- Preferred: parse
compare/vX...vYfrom the existing body. - Fallback:
git describe --tags --abbrev=0 <tag>^to get the tag before<tag>. - First-ever tag (no previous tag exists): fetch all merged PRs up to the tag date; if more than 50, take the 50 most recent and flag it for the user to review.
- Preferred: parse
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.
- 4d ago First seen · 87 lines · 58 tokens per session scan A ed2adc9ebefa
release-notes is a skill published in the GitHub repository samanhappy/mcphub (2,356 stars, last pushed 2d ago), licensed Apache-2.0. It adds 58 tokens to every session and 1,373 once invoked, about $0.0003 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
release-checklist
Pre-release safety audit for the Bifrost repo. Scans database migrations changed in a release for high-scale deadlock / lock-contention risks and for work that blocks application boot time, then produces a pass/warn/fail report with a concrete remediation plan. Invoked with /release-checklist [git-ref-range]. Built to…
release-notes
Create release notes for a new version tag. Gathers all commits, PRs, issues fixed, and breaking changes since a previous release. Creates the release notes markdown file, tags the repo, and pushes. Asks the user to confirm the base version to diff against.
portainer-mcp-release
How to cut a portainer-mcp release that bumps the embedded Portainer OpenAPI spec to a new Portainer minor (e.g. 2.41.x → 2.42.x). Walks through finding the upstream patch target, regenerating the spec, recounting ops/tags per profile, refreshing the orphan-tag inventory, bumping version pins across the README and…
prepare-release
Prepare a new touchdesigner-mcp release: inspect the unreleased diff since the last tag, decide independently how the MCP package version and the MCP API version each move (the API axis stays put unless the server/API contract changed), write the CHANGELOG entry, bump the six version-bearing files, commit, and open…
release-test-audit
Audit whether the unreleased touchdesigner-mcp diff (since the last tag) is adequately covered by integration tests before a release is cut. Walks every API/MCP surface change in the release range, maps each to the integration suite that should cover it, and reports covered / gap / waived per change. Use before…
polish-docs-meta
Finalize documentation and project metadata for a ship-ready release. Use after implementation is complete, tests pass, and devcheck is clean. Safe to run at any stage — each step checks current state and only acts on what still needs work.