Borrowing it
Nothing to install: this file belongs to neptaco/mcproc. 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/neptaco/mcproc/main/.claude/skills/release-preview/SKILL.mdgit clone --depth 1 https://github.com/neptaco/mcprocWrote 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/neptaco/mcproc/release-preview)<a href="https://agentmods.dev/skills/neptaco/mcproc/release-preview"><img src="https://agentmods.dev/badge/skills/neptaco/mcproc/release-preview/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/neptaco/mcproc/release-preview"><img src="https://agentmods.dev/badge/skills/neptaco/mcproc/release-preview.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00044 | $0.00548 |
| Opus 5.5 | $0.00018 | $0.00219 |
| Sonnet 5.5 | $0.00009 | $0.00110 |
| Haiku 4.5 | $0.00004 | $0.00055 |
Grade A, and why
release-preview 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 2mo 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.
What it actually says
リリースプレビュー
次回リリースに含まれる変更をプレビューします。
実行手順
以下のコマンドを順番に実行してください：
1. 現在の状態確認
git describe --tags --abbrev=0 2>/dev/null || echo "タグなし"
git branch --show-current
git status --short
2. 前回リリースからのコミット一覧
最新タグがある場合：
git log --oneline --no-merges $(git describe --tags --abbrev=0)..HEAD
タグがない場合：
git log --oneline --no-merges -20
3. CHANGELOG の Unreleased セクション確認
CHANGELOG.md の先頭部分を確認し、Unreleased セクションがあるか確認：
head -50 CHANGELOG.md
4. 変更の分類
コミット一覧から以下を分類して報告：
リリースノートに含まれるもの：
feat:新機能fix:バグ修正BREAKING CHANGE:破壊的変更
リリースノートに含まれないもの：
docs:,test:,chore:,ci:,build:,refactor:,style:,perf:
5. 推奨バージョンの提示
| 変更タイプ | 次のバージョン |
|---|---|
| BREAKING CHANGE あり | メジャーアップ（例: v1.x.x → v2.0.0） |
| feat: あり | マイナーアップ（例: v1.0.x → v1.1.0） |
| fix: のみ | パッチアップ（例: v1.0.0 → v1.0.1） |
6. 品質チェック
cargo fmt -- --check && cargo clippy --all-targets -- -D warnings && cargo test
次のステップ
リリースを実行する場合：
/release v<VERSION>
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.
- 2mo ago First seen · 76 lines · 44 tokens per session scan A 450f1a11fd5d
release-preview is a skill published in the GitHub repository neptaco/mcproc (10 stars, last pushed 25d ago), licensed MIT. It adds 44 tokens to every session and 548 once invoked, about $0.0002 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
release-rollback
Roll a release back for real when post-deploy regression goes red — apc release rollback flips the current version to pulled and the last good version back to current in the release ledger, and (with --mirror) repoints the bare mirror ref. Behind an approval gate; with no previous good version it BLOCKS instead of…
devops/changelog-generation
A method for creating a CHANGELOG, a document that records what changed in each software release. It reads Git commit history and release-pipeline reports, then groups changes using common commit and changelog conventions.
get-unpublished-changes
Compare HEAD with the latest published npm versions and list all unpublished changes by release layer. Triggers: unpublished changes, changelog, what changed, whats new.
github-release-briefing-skill
Create a source-linked briefing for the latest published GitHub release of a public repository. Use for engineering teams tracking a dependency release; do not use it to publish releases or change repositories.
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…
generate-release-notes
Generate categorized release notes from any source (GitHub, Linear, Jira, or manual input) with optional publishing.