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 commands/akiojin/playfab-mcp-server/releasegit clone --depth 1 https://github.com/akiojin/playfab-mcp-serverWrote 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/commands/akiojin/playfab-mcp-server/release)<a href="https://agentmods.dev/commands/akiojin/playfab-mcp-server/release"><img src="https://agentmods.dev/badge/commands/akiojin/playfab-mcp-server/release.svg" alt="Measured on agentmods" 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.00023 | $0.00436 |
| Opus 5 | $0.00012 | $0.00218 |
| Sonnet 5 | $0.00005 | $0.00087 |
| Haiku 4.5 | $0.00002 | $0.00044 |
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 5d 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
リリースコマンド
develop から main への Release PR を作成し、マージ後に完全自動リリースフローを実行します。
実行内容
gh workflow run prepare-release.yml --ref developを実行- develop → main の Release PR を作成
- CI チェック通過後、Release PR が main に自動マージ
- GitHub Actions が以下を自動実行:
- release.yml (main): release-please でタグ・GitHub Release・Release PR を作成
- *publish.yml (v tag)**: npm publish
前提条件
- develop ブランチにリリース対象コミットが揃っていること
- GitHub CLI (
gh) が認証済み (gh auth login) - 最新コミットが Conventional Commits 形式であること
feat:またはfix:コミットが存在すること
コマンド実行
gh workflow run prepare-release.yml --ref develop
Release PR の確認と操作
# Release PR を確認
gh pr list --base main --head develop
# Release PR を手動マージ（自動マージが有効でない場合）
gh pr merge <PR番号> --merge
トラブルシューティング
- Release PR が作成されない場合は、develop ブランチから main へのコミットがあるか確認してください。
- release.yml が失敗した場合は、Actions から再実行し、ログを確認してください。
- npm publish が有効な場合は
NPM_TOKENが正しく設定されていることを確認してください。 - Release PR が既に存在する場合は、既存の PR を確認して対応してください。
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.
- 5d ago First seen · 48 lines · 23 tokens per session scan A 6305548f1663
release is a command published in the GitHub repository akiojin/playfab-mcp-server (3 stars, last pushed 2d ago), licensed MIT. It adds 23 tokens to every session and 436 once invoked, about $0.0001 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 commands, from other repositories
create-pr
Rebase from the latest origin/main, squash the commits from it, and then create a PR on github with intelligent commit messages based on staged changes. Invoke with /create-pr.
push-and-release
Git pull, resolve conflicts, push, fix hook errors, then release.
land
Cadence-tick autonomous PR babysitter (CI-fix, resolve, converge, merge, close, release).
release
Create a release branch, run changeset version, review changelog, and prepare PR.
release
This compatibility command keeps /oh-my-claudecode:release available without loading the full release skill description in every Claude Code session.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.