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/local-exec-handoff)<a href="https://agentmods.dev/skills/s977043/plangate/local-exec-handoff"><img src="https://agentmods.dev/badge/skills/s977043/plangate/local-exec-handoff.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.00082 | $0.02940 |
| Opus 5 | $0.00041 | $0.01470 |
| Sonnet 5 | $0.00016 | $0.00588 |
| Haiku 4.5 | $0.00008 | $0.00294 |
Grade A, and why
local-exec-handoff 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Local Exec Handoff (PlanGate / Codex 共用)
PlanGate は Claude Code / Codex CLI ともローカル実行が原則。本 skill は ローカルでの exec 再開・ツール間引き継ぎ に使う短いパケットを組み立てる（Codex Cloud 用は manual-cloud-task を参照）。
Read First
参照解決順（導入先で必ずこの順に探す）
本 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 へ進む
- どちらにも無い場合は 「解決できなかった」と明示し、推測で内容を補わない
（packet に「正本
<path>を参照できなかった」旨を書く）
手順 3 に落ちても判定基準は緩めない: 正本が引けない場合でも、本 skill「Rules」節 （C-3 未承認なら exec 再開を拒否 / EH-8 Privacy 準拠 / 受け手の環境に合わせたコマンド表記）と 「Deliverable」の必須項目はすべて満たす。正本を参照できないことを理由に判定基準・ ゲートを緩めてはならない（とくに
approvals/c3.jsonの APPROVED 確認は省略不可）。
| 参照 | install.sh --claude 経由 |
plugin（Claude marketplace）経由 | Codex 経由 |
|---|---|---|---|
rules/*.md（下記 3） |
.claude/rules/ に着地（解決可） |
<plugin_root>/rules/ で解決 |
未配置（解決不可 → 手順 3 へ） |
bin/**（CLI） |
コピー対象外（解決不可） | バンドル対象外（解決不可） | 未配置（解決不可） |
scripts/** |
コピー対象外（解決不可） | <plugin_root>/scripts/ は存在するが install-plangate-skills.sh のみ（codex-guarded.sh 等は解決不可） |
未配置（解決不可） |
docs/working/TASK-XXXX/*（下記 4〜7）は配布物ではなく導入先で作成する作業成果物なので、
導入先リポジトリ内でそのまま解決する。
読む順序
CLAUDE.mdAGENTS.md.claude/rules/working-context.md→ fallback<plugin_root>/rules/working-context.md（current-state.md / status.md 役割分担の正本）docs/working/TASK-XXXX/INDEX.mddocs/working/TASK-XXXX/current-state.mddocs/working/TASK-XXXX/status.md（最終セクション）docs/working/TASK-XXXX/approvals/c3.json（APPROVED 確認）
Rules
- C-3 未承認なら exec 再開を拒否（
approvals/c3.jsonが承認済みであること。legacy はc3_status: APPROVED、c3-prime（approval_kind: "c3-prime"）はdecision: "AUTO_APPROVED"+ Plan Package 束縛検証。判定手順の正本はai-dev-execskill「前提条件（exec 開始ゲート）」節） - handoff packet は 次の担当者が 1 分で再開できる粒度
- 機密情報（events.ndjson / 個人情報 / 認証情報）を含めない（EH-8 Privacy 準拠）
- ツール依存（Claude Code 固有コマンド等）を含めず、PlanGate 共通 CLI（
plangate/./scripts/ai-dev-workflow）に統一する。コマンド表記は packet の受け手の実行環境に合わせる（上流リポジトリの cwd ならbin/plangate、導入先で PATH を通しているならplangate、CLI が無いなら手順を文章で書く。「CLI 呼び出し」節参照）。ai-dev-workflowは PATH に載るインストール経路が無いため、単体名で書かず必ず./scripts/ai-dev-workflow TASK-XXXX <sub>と書く（成立するのは上流リポジトリの cwd のみ。scripts/は配布対象外なので導入先の packet には書かない）
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 · 104 lines · 82 tokens per session scan A 9117eb127b17
local-exec-handoff is a skill published in the GitHub repository s977043/PlanGate (2 stars, last pushed today), licensed MIT. It adds 82 tokens to every session and 2,940 once invoked, about $0.0004 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.