Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/sean-sunagaku/claude-code-pluginnpx agentmods add skills/sean-sunagaku/claude-code-plugin/hook-publisherWrote 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/sean-sunagaku/claude-code-plugin/hook-publisher)<a href="https://agentmods.dev/skills/sean-sunagaku/claude-code-plugin/hook-publisher"><img src="https://agentmods.dev/badge/skills/sean-sunagaku/claude-code-plugin/hook-publisher.svg" alt="Measured on agentmods" 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.00137 | $0.01515 |
| Opus 5 | $0.00068 | $0.00758 |
| Sonnet 5 | $0.00027 | $0.00303 |
| Haiku 4.5 | $0.00014 | $0.00152 |
Grade A, and why
hook-publisher 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 8d 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 — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hook Publisher
Hook スクリプトを claude-code-plugin リポジトリの正しい構造に配置する。
対象リポジトリ
PLUGIN_REPO=/Users/babashunsuke/Repository/claude-code-plugin
リポジトリ構成（Hook プラグイン）
claude-code-plugin/
├── <category>/ # カテゴリ別ディレクトリ
│ └── <hook-plugin-name>/ # 公開用
│ ├── hooks/
│ │ └── <hook-name>/
│ │ ├── hook.py (or hook.sh)
│ │ └── test.py (or test.sh)
│ └── plugin.json # hook 設定 + メタデータ
├── .internal/ # 内部用
│ └── <hook-plugin-name>/
│ ├── hooks/...
│ └── plugin.json
└── .claude-plugin/
└── marketplace.json
カテゴリ一覧
| カテゴリ | 内容 |
|---|---|
agent-toolkit |
エージェントチーム構築・運用 |
review |
コードレビュー・品質チェック |
| その他 | product, planning, design, development, marketing |
plugin.json の構成
Hook プラグインの plugin.json には hook の登録設定を含める:
{
"name": "<hook-plugin-name>",
"version": "<version>",
"description": "...",
"hooks": {
"<HookEvent>": [
{
"matcher": "<ToolName>",
"hooks": [
{
"type": "command",
"command": "python3 \"$HOME/.claude/plugins/cache/<marketplace>/<hook-plugin-name>/<version>/hooks/<hook-name>/hook.py\""
}
]
}
]
}
}
HookEvent: PreToolUse, PostToolUse, Stop など。
ポータブルな command パスのルール
重要: hook の command はプロジェクトの cwd から相対パスで実行される。 プラグインのキャッシュディレクトリは自動解決されないため、以下のルールに従うこと:
$HOMEを使う - ユーザー間でポータブルにするため絶対パスの先頭は$HOMEにする- キャッシュパスの構造:
$HOME/.claude/plugins/cache/<marketplace>/<plugin-name>/<version>/hooks/<hook-name>/hook.py - バージョンはハードコード OK - plugin.json はバージョンごとにパッケージされるため、version 部分はそのバージョンの値を直接書く
- marketplace 名を含める - 例:
sunagaku-marketplace
例（sunagaku-marketplace の agent-teams-log v1.0.0）:
python3 "$HOME/.claude/plugins/cache/sunagaku-marketplace/agent-teams-log/1.0.0/hooks/log-agent-messages/hook.py"
NG パターン（プロジェクトローカル依存）:
python3 .claude/hooks/log-agent-messages/hook.py
→ プロジェクトにファイルがないと動かない。プラグインのインストールだけで完結しない。
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 150 lines · 137 tokens per session scan A a4b4874ff609
hook-publisher is a skill published in the GitHub repository sean-sunagaku/claude-code-plugin (36 stars, last pushed 1mo ago), licensed MIT. It adds 137 tokens to every session and 1,515 once invoked, about $0.0007 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…