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/releasenpx skills add neptaco/mcproc --skill releasegit 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.00040 | $0.01020 |
| Opus 5 | $0.00020 | $0.00510 |
| Sonnet 5 | $0.00008 | $0.00204 |
| Haiku 4.5 | $0.00004 | $0.00102 |
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 yesterday.
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 — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
リリースワークフロー
新しいバージョン $ARGUMENTS をリリースします。
前提条件
- main ブランチにいること
- 未コミットの変更がないこと
- CI が通っていること
手順
1. 事前確認
# 現在のブランチとステータス確認
git branch --show-current
git status --short
未コミットの変更がある場合は、先にコミットまたは stash してください。
2. バージョン決定
引数でバージョンが指定されていない場合、以下を確認：
# 最新のタグを確認
git describe --tags --abbrev=0 2>/dev/null || echo "タグなし"
# 前回リリースからの変更を確認
git log $(git describe --tags --abbrev=0 2>/dev/null)..HEAD --oneline
Semantic Versioning ガイド
| 変更内容 | バージョン | 例 |
|---|---|---|
| 破壊的変更（BREAKING CHANGE） | メジャー | v1.0.0 → v2.0.0 |
| 新機能追加（feat:） | マイナー | v1.0.0 → v1.1.0 |
| バグ修正（fix:） | パッチ | v1.0.0 → v1.0.1 |
3. 品質チェック
cargo fmt -- --check && cargo clippy --all-targets -- -D warnings && cargo test
4. CHANGELOG 更新
CHANGELOG.md の [Unreleased] セクションを新しいバージョンに変更：
## [Unreleased]を## [<VERSION>] - <TODAY>に変更- ファイル末尾のリンク定義を更新
5. Cargo.toml バージョン更新
ワークスペースの Cargo.toml を更新：
[workspace.package]
version = "<VERSION>"
6. 変更をコミット
git add CHANGELOG.md Cargo.toml
git commit -m "chore: bump version to <VERSION>"
7. タグ作成とプッシュ
# タグを作成
git tag -a v<VERSION> -m "Release v<VERSION>"
# コミットとタグをプッシュ（GitHub Actions が自動でリリース）
git push origin main
git push origin v<VERSION>
8. リリース確認
GitHub Actions でリリースワークフローが実行される：
- テスト実行
- クロスプラットフォームビルド（Linux x86_64/arm64, macOS x86_64/arm64）
- GitHub Release 作成（バイナリ添付）
# ワークフロー状態確認
gh run list --workflow=release.yml --limit 3
9. Homebrew 更新
リリースが完了したら、Homebrew Formula を更新：
# publish-homebrew ワークフローを手動実行
gh workflow run publish-homebrew.yml
または homebrew-tap リポジトリで手動更新。
10. リリース完了確認
# GitHub Release を確認
gh release view v<VERSION>
# または Web で確認
gh release view v<VERSION> --web
使用例
/release v0.1.4
/release v0.2.0
/release v1.0.0
トラブルシューティング
タグを削除したい場合
# ローカルタグ削除
git tag -d v<VERSION>
# リモートタグ削除（未リリースの場合のみ）
git push origin :refs/tags/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.
- yesterday First seen · 150 lines · 40 tokens per session scan A df32b61dc1b1
release is a skill published in the GitHub repository neptaco/mcproc (10 stars, last pushed 8d ago), licensed MIT. It adds 40 tokens to every session and 1,020 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
auth-web-cloudbase
CloudBase Web Authentication Quick Guide for frontend integration after auth-tool has already been checked. Provides concise and practical Web authentication solutions with multiple login methods and complete user management.
fix-codesign-error
Slash command that inspects a macOS signing or entitlement failure and explains the minimum fix path. Invoke explicitly with /fix-codesign-error — this skill never self-triggers.
browse-and-evaluate
Use when exploring the ai-agent-skills catalog to find, compare, and evaluate skills before installing. Always use --fields to limit output size and --dry-run before committing to an install.
specflow-use
To connect Rosetta with Grid Dynamics SpecFlow MCP; only when SpecFlow is mentioned and the MCP is installed.
loop-engineering
Shared loop-engineering reference for COG skills - the agent loop, deterministic verifiers, termination conditions, in-loop context management, and named patterns. Invoke when designing or debugging a skill that iterates (search-verify-retry, scan-until-dry, fetch-retry-gate).
telnyx-messaging-hosted-curl
Set up hosted SMS numbers, toll-free verification, and RCS messaging. Use when migrating numbers or enabling rich messaging features. This skill provides REST API (curl) examples.