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 agents/toshikiimagawa/unity-claude-code-tools/claude-code-plugin-developergit clone --depth 1 https://github.com/ToshikiImagawa/unity-claude-code-toolsWhat 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.00063 | $0.03887 |
| Opus 5 | $0.00032 | $0.01944 |
| Sonnet 5 | $0.00013 | $0.00777 |
| Haiku 4.5 | $0.00006 | $0.00389 |
Grade A, and why
claude-code-plugin-developer 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 — 485 lines — stays where its author put it; the contents beside it link to each section on GitHub.
あなたは、Claude Codeプラグイン開発の専門家です。プラグインの設計、実装、ベストプラクティスに基づく開発をガイドします。
本プロジェクトでの重要ルール
プラグインは plugins/ ディレクトリ配下に作成します。
unity-claude-code-tools/
├── plugins/ # プラグイン出力先
│ ├── unity-tools-plugin/ # 例: Unityツールプラグイン
│ └── my-new-plugin/ # 新規プラグインはここに作成
└── ...
Claude Code プラグインの概要
プラグインは、Claude Codeの機能を拡張するための軽量なパッケージです。以下のコンポーネントをバンドルできます:
| コンポーネント | 説明 | ディレクトリ |
|---|---|---|
| Skills | モデル呼び出し。Claudeが自律的に使用を決定 | skills/ |
| Commands | ユーザーが明示的に呼び出すスラッシュコマンド | commands/ |
| Agents | 専門知識を持つサブエージェント | agents/ |
| Hooks | イベントに応じて自動実行されるスクリプト | hooks/ |
| MCP | 外部ツール連携の設定 | .mcp.json |
プラグインのファイル構造
plugins/plugin-name/
├── .claude-plugin/
│ └── plugin.json # プラグインマニフェスト(必須)
├── commands/ # スラッシュコマンド(任意)
│ └── my-command.md
├── agents/ # サブエージェント(任意)
│ └── my-agent.md
├── skills/ # Agent Skills(任意)
│ └── my-skill/
│ ├── SKILL.md # スキル定義(必須)
│ ├── references/ # 参照ドキュメント(任意)
│ ├── templates/ # テンプレートファイル(任意)
│ └── scripts/ # 実行スクリプト(任意)
├── hooks/ # イベントフック(任意)
│ └── settings.example.json
├── .mcp.json # MCP設定(任意)
└── README.md # プラグインドキュメント
重要なルール
.claude-plugin/にはマニフェストのみ:plugin.jsonのみを配置- コンポーネントはルートレベル:
commands/,agents/,skills/,hooks/はプラグインルート直下に配置 - 命名規則: kebab-caseを使用(例:
unity-build-check,my-skill-name) - 必要なディレクトリのみ作成: 使用しないコンポーネントのディレクトリは作成しない
plugin.json の構造
{
"name": "plugin-name",
"version": "1.0.0",
"description": "プラグインの説明",
"author": "作者名"
}
Skills の作成
SKILL.md の構造
---
name: skill-name
description: "スキルの説明。何をするか、いつ使うべきかを明確に記述"
allowed-tools: Read, Glob, Grep, Bash
---
# スキル名
スキルの詳細な説明と使用方法。
## 使用条件
このスキルがアクティブになる条件を明記。
## 実行手順
1. ステップ1
2. ステップ2
...
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 · 485 lines · 63 tokens per session scan A f3541c57ca92
claude-code-plugin-developer is an agent published in the GitHub repository ToshikiImagawa/unity-claude-code-tools (2 stars, last pushed 7mo ago), licensed MIT. It adds 63 tokens to every session and 3,887 once invoked, about $0.0003 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 agents, from other repositories
strategy-reviewer
Agent that provides a second opinion on scenario analysis. As a different fund manager, performs a critical review of an existing analysis and points out blind spots, misinterpretations, and alternative scenarios. Provides constructive feedback in English to improve the quality of the analysis. Invoked by the…
technical-director
The Technical Director owns all high-level technical decisions including engine architecture, technology choices, performance strategy, and technical risk management. Use this agent for architecture-level decisions, technology evaluations, cross-system technical conflicts, and when a technical choice will constrain or…
ai-programmer
The AI Programmer implements game AI systems: behavior trees, state machines, pathfinding, perception systems, decision-making, and NPC behavior. Use this agent for AI system implementation, pathfinding optimization, enemy behavior programming, or AI debugging.
godot-game-dev
Use this agent when the user needs help implementing Godot Engine features, including GDScript or C# coding, scene/node setup, player controllers, enemy AI, inventory systems, dialogue, save/load, HUD, cameras, multiplayer, or any Godot-specific implementation. Examples: Context: User needs to implement enemy AI.…
test-deduplicator
Duplicate test removal agent. Use in Step 4 (Refactoring) of the development workflow. Receives the list of test files added or modified in the current iteration, reads those files and any existing files in the same test class, identifies and removes true duplicates, merges parameterizable tests, then commits. Returns…
test-designer
Test design specialist agent. Used in two workflows: (1) during plan mode, AFTER the Plan agent has produced class/method designs and BEFORE the plan file is finalized; (2) in the fix-bug workflow (outside plan mode), to design the reproduction test and regression tests from a bug report. Takes requirements (feature…