Borrowing it
Nothing to install: this file belongs to Mink16/xserver-mcp. 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/Mink16/xserver-mcp/main/.claude/skills/release/SKILL.mdgit clone --depth 1 https://github.com/Mink16/xserver-mcpWrote 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/mink16/xserver-mcp/release)<a href="https://agentmods.dev/skills/mink16/xserver-mcp/release"><img src="https://agentmods.dev/badge/skills/mink16/xserver-mcp/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/mink16/xserver-mcp/release"><img src="https://agentmods.dev/badge/skills/mink16/xserver-mcp/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.00108 | $0.03728 |
| Opus 5.5 | $0.00043 | $0.01491 |
| Sonnet 5.5 | $0.00022 | $0.00746 |
| Haiku 4.5 | $0.00011 | $0.00373 |
Grade A, and why
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 — 232 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release workflow for xserver-mcp
ultrathink してから実行する。リリースは push / tag / GitHub Release / npm publish / provenance 署名 / CHANGELOG / comparison link を同時に整合させる必要があり、1 個ズレると生態系 (npm 上 dependents / GitHub release 一覧 / compare link) に長期のノイズを残す。npm は同じ version を再 publish できないので、取り返しのつかないポイント (tag push 以降) を最初に特定しておく。
引数 $ARGUMENTS があれば version bump 入力として解釈する (patch / minor / major / v0.2.0 等)。空なら Gate 1 でユーザーに確認する。
When to use / When NOT to use
Use: [Unreleased] に未リリース項目が溜まって新 npm バージョンを生み出したい / 依存更新をまとめて出したい / hotfix を本番に流したい。
Skip: タグを切らない merge / CHANGELOG だけ更新したい / 別リポジトリ / npm publish 回避 / ベースブランチ変更・メジャーアーキテクチャ移行 (先にユーザーと方針決定)。
Prerequisites (repo 固有の契約)
整っていない状態で強行すると OIDC publish が落ちる。壊れているなら skill で直さずユーザーに差し戻す。
.github/workflows/release.ymlがrelease: published+workflow_dispatchで起動し、npm publish --provenance --access publicを走らせる- npmjs.com で GitHub Actions が trusted publisher として登録済 (NPM_TOKEN 不要)
mainに branch protection (required checks + PR 必須) が設定済で admin bypass で push 可能 (solo maintainer 運用)CHANGELOG.mdが Keep a Changelog 形式 + 末尾に[x.y.z]: <compare url>の comparison link を持つpackage.jsonのversionが CHANGELOG の直近タグと一致している
Upstream contract (github-flow 側の前提)
この skill は github-flow が正しく回っている前提で起動する (詳細: .claude/rules/github-flow.md#release-への接続)。具体的には:
- user-facing な変更を含む各 PR が merge 時に
CHANGELOG.mdの## [Unreleased]に 1 行追記している (PR チェックリスト項目) - 従って release 起動時には
[Unreleased]を見れば「このバージョンで何が出るか」がほぼ確定している
[Unreleased] が空 or 明らかに不足している場合は Step 2 で git log から補完するフォールバック経路があるが、これは例外処理であって通常経路ではない。毎回フォールバックが走るなら PR 側の運用が崩れているサインなので、release を進める前にユーザーに差し戻して upstream の習慣を直してもらう。
Inputs (ユーザーから集める)
- Version bump:
$ARGUMENTSでpatch/minor/major/v0.2.0いずれか。未指定ならgit log <last-tag>..HEAD --onelineを読んで conventional commits から提案する:- 0.x 期:
BREAKING/feat!:→ minor、それ以外 (feat/fix/perf/docs/chore等) → patch - 1.0 以降: SemVer 通常 (breaking → major、feat → minor、それ以外 → patch)
- 0.x 期:
- Release notes 粒度:
[Unreleased]が既に埋まっているなら表記・順序の整形提案のみ。空ならgit log --oneline <last-tag>..HEADを conventional commits 種別でグループ化して下書きする。
What ships with it
1 file 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 · 232 lines · 108 tokens per session scan A d0dadaa96c88
release is a skill published in the GitHub repository Mink16/xserver-mcp (0 stars, last pushed 4mo ago), licensed MIT. It adds 108 tokens to every session and 3,728 once invoked, about $0.0004 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
git-wrapup
Land working-tree changes as logical commits — the work grouped by concern, topped by a release commit (version bump, changelog, regenerated artifacts). The work commits land first, then the version bump, verification, and the release commit on top. Stops at "committed locally on main" — or, when the project releases…
release-and-publish
Ship a release end-to-end across every registry the project targets (npm, MCP Registry, GitHub Releases for .mcpb bundles, GHCR). Runs the final verification gate, fast-forwards main when the release rode a release PR, creates the annotated tag on the commit main now points at, pushes commits and tags, then publishes…
release-pr-review
Review pass on an open release PR (release/ → main) — the step between git-wrapup and release-and-publish when a project releases in gated release PR mode. Reads the PR's commit range through the code-simplifier lens plus a correctness review, verifies whatever an automated reviewer left on the PR, lands fixes as…
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-and-publish
Ship a release end-to-end across every registry this project targets (npm, MCP Registry). Runs the final verification gate, pushes commits and tags, then publishes to each applicable destination. Assumes git wrapup (version bumps, changelog, commit, annotated tag) is already complete — this skill is the post-wrapup…
bob-export
Create a Hacker Bob post-release improvement bundle for the currently installed Bob version.