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 skills add megaphone-tokyo/kioku --skill marketing-release-handoffgit clone --depth 1 https://github.com/megaphone-tokyo/kiokuWrote 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/megaphone-tokyo/kioku/marketing-release-handoff)<a href="https://agentmods.dev/skills/megaphone-tokyo/kioku/marketing-release-handoff"><img src="https://agentmods.dev/badge/skills/megaphone-tokyo/kioku/marketing-release-handoff/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/megaphone-tokyo/kioku/marketing-release-handoff"><img src="https://agentmods.dev/badge/skills/megaphone-tokyo/kioku/marketing-release-handoff.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.00180 | $0.03372 |
| Opus 5 | $0.00090 | $0.01686 |
| Sonnet 5 | $0.00036 | $0.00674 |
| Haiku 4.5 | $0.00018 | $0.00337 |
Grade A, and why
marketing-release-handoff 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 12d 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 — 241 lines — stays where its author put it; the contents beside it link to each section on GitHub.
marketing-release-handoff
KIOKU の release 直後に PM session (本 skill 起動者) がマーケ部に投げる引き継ぎ資料 を構造化して生成する skill。バグ fix や内部改善は除外し、user が touch できる価値 + 訴求角度 + 記事ネタ のみに絞った markdown を tools/claude-brain/marketing/handoff/ に保存する。
いつ使うか
- KIOKU の release (v0.X.Y tag) を publish した直後
- マーケ部に「何が出たか / 何を訴求できるか」を PM side から説明したい時
- 記事ネタ候補 (dev.to / Qiita / Zenn) を構造化して引き渡したい時
使わない場面:
- Patch release (v0.X.Y hotfix) で user-facing な変化が無い時 → 手動で省略判断
- マーケ担当が自力で Changelog 解読する運用に戻したい時 → 本 skill は PM→マーケ の橋渡し用
前提
- release 作業 (tag + .mcpb + GitHub Release + README Changelog 10 言語) が既に完了していること
tools/claude-brain/app/README.mdの Changelog に 対象 version の entry が存在すること- 参照正典:
tools/claude-brain/marketing/handoff/kioku-marketing-handover.md(マーケ運用鉄則)、.claude/rules/marketing.md(マーケ関連 file 配置ルール)
起動
/marketing-release-handoff v0.7.0
引数省略時 (/marketing-release-handoff) は kioku 最新 tag を gh api repos/megaphone-tokyo/kioku/tags で自動検出。
実行手順 (skill 本体の処理)
Step 1: Release info 収集
-
VERSION を確定: slash command 引数 (例:
/marketing-release-handoff v0.7.0のv0.7.0) が与えられていればそれを使う。省略時は latest tag を Bash で取得:gh api 'repos/megaphone-tokyo/kioku/tags?per_page=1' --jq '.[0].name'※ この snippet 内の
$1/${1:-...}を slash command 引数と混同しないこと。skill は引数を prompt 文脈で受け取り、shell 位置引数は空。<VERSION>は以降v0.7.0等の確定値に置換して使う。 -
tag 情報と published 日を取得:
gh release view "<VERSION>" --repo megaphone-tokyo/kioku --json tagName,publishedAt,assets -
handoff filename の日付 + NN 連番を決定: publishedAt を YYMMDD 形式に変換 (例: 2026-04-24 → 260424)、NN は既存 handoff の同日件数 +1 を
ls tools/claude-brain/marketing/handoff/ | grep "^<YYMMDD>"で数えて決定 (該当無しなら01)。
Step 2: Changelog 該当 entry 抽出 (LEARN#10 準拠)
-
必ず 以下 grep で heading 実在を verify (LEARN#10 精読必須):
grep -n "^### .*— <VERSION>:" tools/claude-brain/app/README.mdhit 無し → 即 abort。推測ベースで handoff 本文を書かず、user に以下を報告:
Changelog entry 未作成の可能性。release cascade (parent PR → sync-to-app → kioku README PR → kioku main merge → post-release-sync) が完了していない疑い。LEARN#11 の 4 step を確認してください。
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.
- 12d ago First seen · 241 lines · 180 tokens per session scan A 5d472b485145
marketing-release-handoff is a skill published in the GitHub repository megaphone-tokyo/kioku (5 stars, last pushed 2mo ago), licensed MIT. It adds 180 tokens to every session and 3,372 once invoked, about $0.0009 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
github-release-management
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.
taiyi-integration
A project workflow skill for closing a TaiyiForge change and recording it in a CHANGELOG.md file. It checks review results, tests, and the state of the working tree before archiving the change.
release
CONTRIBUTOR TOOL - Cut a plugin release: bump plugin.json version, finalize CHANGELOG, update README if needed, gate on make ci, commit, tag vX.Y.Z, and create the GitHub release. Use when shipping a new plugin version. NOT distributed.
commit-pr
Mandatory Codex/Copilot publication adapter for opencode-swarm. Use for every GitHub issue assignment that results in code changes, commits, pushes, draft PRs, PR body edits, PR readying, release notes, or CI closeout. Must be loaded before git push, gh pr create, gh pr edit, or gh pr ready. Routes to the single…
git-workflow
Guides you through Git workflows — branching strategies, commit conventions, merge conflict resolution, and release management. Use when working with Git repositories or when the user asks about version control best practices.
no-mistakes
Validate committed feature-branch changes through the no-mistakes pipeline: intent, rebase, review, test, docs, lint, push, PR, and CI. Use when the user asks to run no-mistakes, ship safely, validate before pushing, or gate a change before it reaches upstream.