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 skills/s977043/plangate/manual-cloud-tasknpx skills add s977043/PlanGate --skill manual-cloud-taskgit clone --depth 1 https://github.com/s977043/PlanGateWrote 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/manual-cloud-task)<a href="https://agentmods.dev/skills/s977043/plangate/manual-cloud-task"><img src="https://agentmods.dev/badge/skills/s977043/plangate/manual-cloud-task.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 | $0.00073 | $0.02164 |
| Opus 5 | $0.00036 | $0.01082 |
| Sonnet 5 | $0.00015 | $0.00433 |
| Haiku 4.5 | $0.00007 | $0.00216 |
Grade A, and why
manual-cloud-task 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 5d 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Manual Cloud Task (PlanGate / optional)
PlanGate での位置付け: PlanGate は Claude Code / Codex CLI どちらもローカル実行が原則。Codex Cloud を使う場合のみ本 skill を使う(optional)。ローカル exec 再開には
local-exec-handoffskill を参照。
Read First
参照解決順(導入先で必ずこの順に探す)
本 skill の参照は上流リポジトリ基準の相対パスで書かれている。導入先ではそのままでは 解決できないものがあるため、次の順で探索する:
- 導入先リポジトリの相対パス(例:
.claude/rules/working-context.md)。 ただし 本 skill が参照する節(例:working-context.mdの「ゲート条件」節)が実在することを確認する。同名でも別内容なら PlanGate の正本ではないため 2 へ進む - 無ければ plugin root 配下(例:
<plugin_root>/rules/working-context.md)。<plugin_root>は Bash でls "${CLAUDE_PLUGIN_ROOT}/rules/"を実行して展開・確認した 絶対パス(Read ツールは絶対パスを要求し環境変数を展開しないため、${CLAUDE_PLUGIN_ROOT}/...という文字列をそのまま Read しない)。変数が空・未設定ならキャッシュを glob で推測せず 3 へ進む - どちらにも無い場合は 「正本
<path>を参照できなかった」と明示し、推測で内容を補わない
plugin root 配下の探索は docs/** には適用しない(手順 2 は rules/*.md 等の
配布対象にのみ適用する): plugin が配布するのは agents / commands / skills / rules 等の
定義ディレクトリのみで docs/ を配布対象として認識せず、plugin root 配下に相当する配布物が
存在しないため必ず空振りする。docs/** は手順 1 で解決できなければ手順 2 を飛ばして手順 3 へ進む。
導入経路ごとに配置されるものが違う:
| 参照 | install.sh --claude 経由 |
plugin(Claude marketplace)経由 | Codex 経由 |
|---|---|---|---|
rules/*.md |
.claude/rules/ に着地(解決可) |
<plugin_root>/rules/ で解決 |
未配置(解決不可 → 手順 3 へ) |
.codex/** / docs/** |
コピー対象外(解決不可) | バンドル対象外(解決不可) | 未配置(解決不可) |
scripts/** / bin/** |
コピー対象外 | 目的の CLI は不在 | 未配置 |
install.sh --claude のコピー対象は agents / skills / commands / rules の 4 ディレクトリ
のみ。Codex 経由(install_codex())は install-plangate-skills.sh を呼ぶだけで skills しか
配置されないため、rules 参照は解決順 1・2 とも成立せず必ず手順 3 に落ちる。
読む順序
CLAUDE.mdAGENTS.md.claude/rules/working-context.md→ fallback<plugin_root>/rules/working-context.md(C-3 / handoff 要件)- どちらでも解決できない場合は、下記「Rules」節の C-3 未承認時の停止条件
(
approvals/c3.jsonAPPROVED 必須)を代替正本とし、Cloud task 指示に 「正本working-context.mdを参照できなかった」旨を記録する
- どちらでも解決できない場合は、下記「Rules」節の C-3 未承認時の停止条件
(
.codex/manual-cloud-task.md(配布対象外。上流リポジトリで作業する場合のみ解決する。 導入先では下記「Deliverable」の転記先を導入先の任意パスに読み替える)
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.
- 5d ago First seen · 106 lines · 73 tokens per session scan A 047999a51f94
manual-cloud-task is a skill published in the GitHub repository s977043/PlanGate (2 stars, last pushed 5d ago), licensed MIT. It adds 73 tokens to every session and 2,164 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.