MCPHub is a self-hosted gateway that connects and manages multiple MCP servers, which provide tools, prompts, and resources to AI applications. Users organize servers into groups, control access, monitor activity and health, and expose stable endpoints to clients such as Claude Code, Cursor, and OpenWebUI; the catalogue entries operate within this MCP environment.
Borrowing it
Nothing to install: this file belongs to samanhappy/mcphub. 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/samanhappy/mcphub/main/.agents/skills/polish-release/SKILL.mdgit 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/polish-release)<a href="https://agentmods.dev/skills/samanhappy/mcphub/polish-release"><img src="https://agentmods.dev/badge/skills/samanhappy/mcphub/polish-release/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/samanhappy/mcphub/polish-release"><img src="https://agentmods.dev/badge/skills/samanhappy/mcphub/polish-release.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.00063 | $0.00846 |
| Opus 5.5 | $0.00025 | $0.00338 |
| Sonnet 5.5 | $0.00013 | $0.00169 |
| Haiku 4.5 | $0.00006 | $0.00085 |
Grade A, and why
polish-release 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.
How it starts
The opening of the file, as written. The whole thing — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Polish Release
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.
Structure contract
The required structure lives in exactly one place: .github/release-notes-template.md (read it). It is enforced by scripts/validate-release-notes.js (CI runs it on publish/edit). The rules:
- Section order must match the template.
Summary,摘要,Referencesmust be present and non-empty.- Each optional English section (
Features/Fixes) and its Chinese pair must appear together — never one without the other. - Optional sections with no content are omitted entirely — never an empty section, never
None/无placeholders. Referencesbullets use the exact format<title> by @<login> in <pull url>, followed by oneFull changelog:line.New Contributorsbullets use@<login> made their first contribution in #<number>.
Workflow
-
Resolve the target release. Use the tag the user gave (e.g.
v1.0.14), else the latest:gh release list --limit 1. -
Generate the deterministic parts.
node scripts/build-release-notes.js <tag>This resolves the previous tag (compare line in the existing body, else
git describe), fetches merged PRs in the range, and prints a draft skeleton to stdout with<<FILL: ...>>markers where you must write content. It reuses the existing body's## New Contributorswhen present and falls back to detecting new contributors itself. It never writes files. -
Write the draft in the conversation (not in the working tree). From the PR list in the skeleton:
## Summary— one English paragraph on why this release matters.## 摘要— Chinese translation of the Summary.## Features/## 功能— user-facing additions (omit if none).## Fixes/## 修复— bug fixes, reliability, dependency bumps (omit if none).- Translate each bullet into Chinese: PR title in Chinese, then
by @<author>and URL as-is. - Keep
## New Contributorsand## Referencesas printed, replacing every<<FILL: ...>>marker. Drop any section whose content is 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.
- 1mo ago First seen · 57 lines · 63 tokens per session scan A d263ba3acc7d
polish-release is a skill published in the GitHub repository samanhappy/mcphub (2,600 stars, last pushed today), licensed Apache-2.0. It adds 63 tokens to every session and 846 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-09-08.
Other skills, from other repositories
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.
create-milestone
Create a GitHub milestone for an upcoming release. Suggests the next version based on the latest release, gathers all merged PRs and closed issues since that release, presents a draft with two tables (Issues and PRs) for user approval, then creates the milestone and assigns all approved items.
release-notes-check
Check a supplied release note for its owner and rollback note.
release-changelog-harness
Chooses ecosystem-native release and changelog tooling (Changesets, Melos, release-plz) plus binary distribution (GitHub Release tarballs, install.sh) when the product is an executable. Use for release CI, install.sh, versioning, CHANGELOGs, shipping MCP/CLI without clone, or meta repos that only ship skills via npx…
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.
release-management
Tag a commit, publish a GitHub release, and read, correct or withdraw the tags and releases already there.