Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/skill-publisher)<a href="https://agentmods.dev/skills/sean-sunagaku/claude-code-plugin/skill-publisher"><img src="https://agentmods.dev/badge/skills/sean-sunagaku/claude-code-plugin/skill-publisher.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.00194 | $0.02004 |
| Opus 5 | $0.00097 | $0.01002 |
| Sonnet 5 | $0.00039 | $0.00401 |
| Haiku 4.5 | $0.00019 | $0.00200 |
Grade A, and why
skill-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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Publisher
スキルを claude-code-plugin リポジトリの正しい構造に配置する。
対象リポジトリ
PLUGIN_REPO=/Users/babashunsuke/Repository/claude-code-plugin
リポジトリ構成
claude-code-plugin/
├── <category>/ # カテゴリ別ディレクトリ
│ └── <skill-name>/ # 公開用
│ ├── .claude-plugin/
│ │ └── plugin.json # プラグインメタデータ（CI 必須）
│ ├── agents/ # サブエージェント定義（あれば）
│ │ └── <agent-name>.md
│ └── skills/<skill-name>/
│ ├── SKILL.md
│ ├── references/ (あれば)
│ ├── scripts/ (あれば)
│ └── assets/ (あれば)
├── .internal/ # 内部用（自分のリポジトリ向け）
│ └── <skill-name>/
│ ├── .claude-plugin/
│ │ └── plugin.json # CI 必須
│ └── skills/<skill-name>/...
└── .claude-plugin/
└── marketplace.json # スキル登録設定（公開・内部どちらも登録が必要）
カテゴリ一覧
| カテゴリ | 内容 |
|---|---|
product |
プロダクト企画・ユーザーリサーチ |
planning |
機能検討・技術設計・実装計画 |
design |
UI/UXデザイン・ロゴ作成 |
development |
CI/CD・DB・Git・デバッグ・テスト |
review |
コードレビュー・品質チェック |
marketing |
アプリ名・ASO・スクリーンショット |
agent-toolkit |
エージェントチーム構築・運用 |
agents/ について
agents/は plugin root 直下に配置（<skill-name>/agents/）- 各
.mdファイルは YAML frontmatter（name,description,tools,model等）+ システムプロンプト - プラグインインストール時に自動検出される（
plugin.jsonへの明示記載は不要）
ワークフロー
Step 1: ソーススキルの特定と配置先の確認
ユーザーに以下を確認:
- コピー元のスキルパス（例:
~/.claude/skills/app-naming/） - または
~/.claude/skills/内のスキル一覧から選択 - カテゴリ: 公開用の場合、どのカテゴリに配置するか（product, planning, design, development, review, marketing, agent-toolkit）
- 配置先: 公開用（カテゴリ配下）か 内部用（
.internal/配下）か - ステータス:
stable（デフォルト）かbetaか - agents/: ソースに
agents/ディレクトリがあるか確認
Step 2: 構造検証
コピー前に検証する:
SKILL.mdが存在するか- YAML frontmatter に
nameとdescriptionがあるか - references/ 内のファイルが SKILL.md から参照されているか
検証スクリプト: scripts/validate-skill.sh <skill-path>
Step 3: 重複チェック
PLUGIN_REPO に同名のスキルが既に存在するか確認。 存在する場合はユーザーに上書きするか確認。
Step 4: コピー・配置
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 · 167 lines · 194 tokens per session scan A de5404e2ff5d
skill-publisher is a skill published in the GitHub repository sean-sunagaku/claude-code-plugin (36 stars, last pushed 1mo ago), licensed MIT. It adds 194 tokens to every session and 2,004 once invoked, about $0.0010 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…