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/s977043/plangate/plangate-setup)<a href="https://agentmods.dev/skills/s977043/plangate/plangate-setup"><img src="https://agentmods.dev/badge/skills/s977043/plangate/plangate-setup.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.00098 | $0.03153 |
| Opus 5 | $0.00049 | $0.01577 |
| Sonnet 5 | $0.00020 | $0.00631 |
| Haiku 4.5 | $0.00010 | $0.00315 |
Grade A, and why
plangate-setup 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 6d 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 — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PlanGate Setup — チェックリスト & 観点
入力: doctor の構造化出力（
--json）/ Human からの「完了」報告 出力: 不足項目リスト / Human-owned 操作の提示文 / 進捗チェックリスト 想定 phase: 初期セットアップ カテゴリ: ガイド型セットアップ 役割: 手順テンプレと検証観点を再利用単位で保持する
参照解決順（導入先で必ずこの順に探す）
本 skill の参照は上流リポジトリ（s977043/plangate）基準の相対パスで書かれている。
導入先ではそのままでは解決できないものがあるため、次の順で探索する:
- 導入先リポジトリの相対パス（例:
.claude/rules/working-context.md） - 無ければ plugin root 配下（例:
<plugin_root>/rules/working-context.md）<plugin_root>は Bash でls "${CLAUDE_PLUGIN_ROOT}/rules/"を実行して得た絶対パス。 Read ツールは絶対パスを要求し環境変数を展開しないため、${CLAUDE_PLUGIN_ROOT}/...という文字列をそのまま Read しても必ず失敗する- 変数が空・未設定なら glob（
~/.claude/plugins/cache/**等）で推測せず 3 へ進む
- どちらにも無い場合は 「解決できなかった」と明示し、推測で内容を補わない
（
status.mdに「正本<path>を参照できなかった」旨を記録する）
手順 3 に落ちても判定基準は緩めない: 正本が引けない場合の代替は「5 要素対応」表の 「検証」列を導入先のファイルで直接確認する手動検証であって、確認の省略ではない。 正本を参照できないことを理由に判定基準・ゲートを緩めてはならない（未検証項目を 「doctor PASS」「確認済み」と書かず、未検証である事実を
status.mdに残す）。
| 参照 | install.sh --claude 経由 |
plugin（Claude marketplace）経由 | Codex 経由 |
|---|---|---|---|
rules/*.md |
.claude/rules/ に着地（解決可） |
<plugin_root>/rules/ で解決 |
未配置（解決不可 → 手順 3 へ） |
bin/**（CLI） |
コピー対象外（解決不可） | バンドル対象外（解決不可） | 未配置（解決不可） |
scripts/** |
コピー対象外（解決不可） | <plugin_root>/scripts/ は存在するが install-plangate-skills.sh のみ（apply-claude-settings.sh 等は解決不可） |
未配置（解決不可） |
CLI 前提（doctor が何を検査するか）
前提（Human 決定 #1144）: plugin /
install.sh --claude/ Codex が導入先へ配るのは 読み物層（skills/rules/agents/commands）だけであり、CLI（PlanGate CLI 本体）も enforcement 層（scripts/hooks/）も配布物に含まれない。doctorを実行できるのは 上流リポジトリ（s977043/plangate）の clone がある環境だけである。導入先の セットアップ検証でdoctorに到達したら「CLI が無いため実行できない／上流リポジトリの clone が必要」と明示して停止するか、下記「5 要素対応」表の「検証」列を導入先の ファイルを直接見て手動確認へ置き換える。CLI が無いことを理由に検証を黙って省略し、 「doctor PASS」と読める記録を残してはならない。
本 skill は doctor を単一検証源とするが、doctor は cwd ではなく CLI 本体の位置を基準に
検査する。bin/plangate は自身のパスから plangate_root（= bin/ の親）を求め、
doctor / doctor --json / doctor --check-settings はいずれも
<CLI の repo root> 配下（.claude/settings.json / .claude/rules/ / docs/working/ /
schemas/ 等）を対象にする。--dir 相当のオプションも無い。
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.
- 6d ago First seen · 171 lines · 98 tokens per session scan A 46b34cb7075a
plangate-setup is a skill published in the GitHub repository s977043/PlanGate (2 stars, last pushed 6d ago), licensed MIT. It adds 98 tokens to every session and 3,153 once invoked, about $0.0005 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
skill-maintenance
Automated skill maintenance tool (v6 — Unified Registry + Snapshots). Full scan: [Orphan] migrate misplaced skills from category dirs OR standalone skills/<name>/ to auto-generated/, [Sync] auto-generated/ vs registry lifecycle diff (new/deleted/revived + description auto-sync via lifecycle field), [Reg]…
extract
Run the full Semantica semantic extraction pipeline on a file or selected text — NER, relations, events, coreference resolution, triplets, and validation. Clears result cache before each run. Returns Markdown tables with entity/relation/event/triplet results and inline validator warnings.
watch
File sentinel that monitors the working directory for changes and marker comments, then auto-triggers appropriate skills. Poll-based via git diff against the last scan commit. Writes intake items for batch processing and routes marker actions through /do. Use for automatic reactions to file changes; do NOT use for…
live-preview
Mid-build visual verification loop. Takes screenshots of components during construction, not just after. Catches visual regressions and invisible features before they compound. Requires Playwright or similar screenshot tool.
review
5-pass structured code review — correctness, security, performance, readability, consistency.
marshal
Meta-orchestrator that takes any direction — broad, specific, or vague — and autonomously chains skills and context into actionable work. Gathers context from codebase, docs, and memory. Only asks the user when it genuinely cannot proceed. Single-session orchestrator.