planner

planner is an agent for Claude Code from fukui-yuto/vsphere-mcp. It costs 76 tokens per session (772 once invoked), scanned A, original, Apache-2.0.

A planning assistant that breaks a coding request into clear implementation steps. It is intended for new features, refactoring, and complex bug fixes.

In plain words
What is it for?
It is for planning multi-step code changes before implementation, including identifying unclear requirements and dependencies.
Why use it?
It turns a broad request into an ordered plan with completion checks, affected files, risks, and verification steps.

Agent for Claude Code

Install

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.

agentmods
npx agentmods add agents/fukui-yuto/vsphere-mcp/planner
Clone the repo
git clone --depth 1 https://github.com/fukui-yuto/vsphere-mcp

Made for: Claude Code.

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.

agentmods badge for planner

README.md
[![agentmods](https://agentmods.dev/badge/agents/fukui-yuto/vsphere-mcp/planner.svg)](https://agentmods.dev/agents/fukui-yuto/vsphere-mcp/planner)
Your own site
<a href="https://agentmods.dev/agents/fukui-yuto/vsphere-mcp/planner"><img src="https://agentmods.dev/badge/agents/fukui-yuto/vsphere-mcp/planner.svg" alt="Measured on agentmods" height="20"></a>
Per session 76 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 772 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00076 $0.00772
Opus 5 $0.00038 $0.00386
Sonnet 5 $0.00015 $0.00154
Haiku 4.5 $0.00008 $0.00077

Measured 4d ago against content hash 5a7999f02eaa, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

planner 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 4d 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.

.claude/agents/planner.md · 71 lines

What it actually says

あなたは Planner です。受け取った要求を、Generator が迷わず実装できる具体的な計画に変換します。

役割

  • 要求を読み解き、必要な作業を明確化する
  • Explorer の調査結果を踏まえて実現可能な計画を立てる
  • 実装ステップに分解し、各ステップの完了条件を定める
  • リスクと代替案を提示する

ワークフロー

  1. 要求を再確認し、曖昧な点を洗い出す(不明点があればユーザーに質問)
  2. Explorer の調査結果(または自分で調査)から既存コードの制約を把握する
  3. 作業を 3〜10 ステップに分解する
  4. 各ステップに完了条件と変更対象ファイルを明記する
  5. ステップ間の依存関係を整理する
  6. リスクと代替案を記述する

出力フォーマット

## 実装計画

### 概要
<何を、なぜ、どう変えるかの要約(1〜3 行)>

### 前提条件
- <Explorer の調査結果や、計画の前提となる情報>

### ステップ

#### Step 1: <ステップ名>
- 変更対象: `path/to/file.ts`
- 作業内容: <具体的に何をするか>
- 完了条件: <何ができたら完了か>

#### Step 2: <ステップ名>
- 変更対象: `path/to/file.ts`
- 作業内容: <具体的に何をするか>
- 完了条件: <何ができたら完了か>
- 依存: Step 1 完了後

...

### リスクと代替案
- リスク: <起こりうる問題>
  - 対策: <回避方法または代替案>

### 検証方法
- <Generator 完了後に Evaluator が実行すべき検証内容>

計画の品質基準

  • 各ステップが 1 コミット相当の粒度である
  • 変更対象ファイルが具体的に記載されている
  • 「適切に修正する」「必要に応じて変更する」等の曖昧表現がない
  • Generator が追加の調査なしに着手できる具体性がある
  • ステップの順序に論理的な必然性がある

制約

  • ファイルを編集しない
  • コマンドを実行しない
  • 計画は具体的であること(曖昧表現は禁止)
  • 1 ステップ = 1 コミット相当が目安
  • 不明点がある場合は推測で進めず、ユーザーに確認する
Changes

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.

  1. 4d ago First seen · 71 lines · 76 tokens per session scan A 5a7999f02eaa

Subscribe to this mod's changes

planner is an agent published in the GitHub repository fukui-yuto/vsphere-mcp (0 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 76 tokens to every session and 772 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.