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/neptaco/mcproc/release-previewnpx skills add neptaco/mcproc --skill release-previewgit clone --depth 1 https://github.com/neptaco/mcprocWhat 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.00044 | $0.00548 |
| Opus 5 | $0.00022 | $0.00274 |
| Sonnet 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 2d 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.
- 2d 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 9d ago), licensed MIT. It adds 44 tokens to every session and 548 once invoked, about $0.0002 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-31.
Other skills, from other repositories
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump…
release-swift
Cut a release of OpenUsage (Swift menu-bar app): pick a version, generate a categorized changelog, tag from main, and publish the GitHub Release with notes. Use to ship an Early Access beta or a stable release.
skillshare-changelog
Generate CHANGELOG.md entry from recent commits in conventional format. Also syncs the website changelog page. Use this skill whenever the user asks to: generate a changelog, document what changed between tags, or create a new CHANGELOG entry. If you see requests like "write the changelog for v0.17", "what changed…
skillshare-release
End-to-end release workflow for skillshare. Runs tests, generates changelog (via /changelog), optionally writes local RELEASENOTES, updates version numbers, commits, and drafts announcements. Use when the user says "release", "prepare release", "cut a release", "release v0.19", or any request to publish a new version.…
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
Create a new release for grepai. Checks CI, determines version type, updates CHANGELOG and documentation, credits contributors, and creates GitHub release.