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/plan-review-gate)<a href="https://agentmods.dev/skills/s977043/plangate/plan-review-gate"><img src="https://agentmods.dev/badge/skills/s977043/plangate/plan-review-gate/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/s977043/plangate/plan-review-gate"><img src="https://agentmods.dev/badge/skills/s977043/plangate/plan-review-gate.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.00062 | $0.03820 |
| Opus 5 | $0.00031 | $0.01910 |
| Sonnet 5 | $0.00012 | $0.00764 |
| Haiku 4.5 | $0.00006 | $0.00382 |
Grade A, and why
plan-review-gate 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 9d 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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan Review Gate (PlanGate / Codex 共用)
PlanGate の plan ゲート（C-1 セルフレビュー / C-2 外部レビュー / C-3 人間承認） を確認する skill。EH-3（plan_hash 改竄検知）と整合する手順順序を担保する。
Read First
CLAUDE.mdAGENTS.md.claude/rules/working-context.md（C-1 / C-3 三値ゲート / 条件付き降格 / settings タスクロック の正本）.claude/rules/review-principles.md（5 観点 / Severity / C-2 2 レーン責務契約の正本）.claude/rules/mode-classification.md（mode 別フェーズ適用マトリクス）docs/working/TASK-XXXX/plan.mddocs/working/TASK-XXXX/review-self.md（C-1）docs/working/TASK-XXXX/review-external.md（C-2、存在すれば）docs/working/TASK-XXXX/approvals/c3.json（存在すれば）
参照解決順（
docs/**/ 導入先で必ずこの順に探す）: 本 Skill が参照するdocs/**は上流リポジトリ基準の相対パスであり、install.sh --claude/ plugin（Claude marketplace）/ Codex の 3 経路とも配布対象外（解決不可）。(1) 導入先リポジトリの同名パスを探す → (2) 見つからなければ 「正本<path>を参照できなかった」と明示し、本 Skill 内の記述を代替正本として扱い、推測で内容を補わない。plugin root 配下の探索はdocs/**には適用しない: plugin が配布するのはagents/commands/skills/rules等の定義ディレクトリのみでdocs/を配布対象として認識せず、plugin root 配下に相当する配布物が存在しないため、plugin root 段を置いても必ず空振りする（クラス A の rules 参照が plugin root 配下で解決できるのはrules/が実際に配布されるからであり、この非対称をdocs/**に持ち込まない）。
参照解決順（.claude/rules/*.md / 導入先で必ずこの順に探す）
本 Skill は C-1 / C-2 / C-3 の判定正本として .claude/rules/working-context.md /
.claude/rules/review-principles.md / .claude/rules/mode-classification.md を参照する
（§Read First 3〜5）。これらのパスは上流リポジトリ基準のため、導入先では 次の順で探索する
（3 本それぞれに適用する）:
- 導入先リポジトリの
.claude/rules/<name>.md。 ただし 本 skill が参照する節（例:working-context.mdの「C-3ゲート（計画承認・三値）」節）が実在することを確認する。同名でも別内容なら PlanGate の正本ではないため 2 へ進む - 無ければ plugin root 配下
<plugin_root>/rules/<name>.md。<plugin_root>は Bash でls "${CLAUDE_PLUGIN_ROOT}/rules/"を実行して展開・確認した 絶対パス（Read ツールは絶対パスを要求し環境変数を展開しないため、${CLAUDE_PLUGIN_ROOT}/...という文字列をそのまま Read しない）。変数が空・未設定ならキャッシュを glob で推測せず 3 へ進む - どちらにも無い場合は 「正本
<name>.mdを参照できなかった」と明示し、 推測で内容を補わない。判定基準を推測で代替して C-1 / C-3 を続行しない
C-1 セルフレビュー
チェック項目の定義と項目数は docs/working/templates/review-self.md を正本とする（現行 全 25 項目）。mode に応じた適用範囲は .claude/rules/working-context.md の C-1 節および .claude/rules/mode-classification.md フェーズ適用マトリクスを正本とする。FAIL があれば修正後再実行。evidence は FAIL 時必須（evidence/c1-review/）。
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.
- 9d ago First seen · 141 lines · 62 tokens per session scan A 2c64fdb4c066
plan-review-gate is a skill published in the GitHub repository s977043/PlanGate (2 stars, last pushed today), licensed MIT. It adds 62 tokens to every session and 3,820 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 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…
review
5-pass structured code review — correctness, security, performance, readability, consistency.
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.
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.