multi-plan

A planning command that gathers project context and asks two coding models to produce a step-by-step implementation plan.

In plain words
What is it for?
Use it to investigate a codebase, validate planning stages, and save implementation plans in .claude/plan files.
Why use it?
It helps compare separate analyses before work begins and keeps planning separate from production-code changes.

Command

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 commands/rohitbind123/claude-setup/multi-plan
Clone the repo
git clone --depth 1 https://github.com/RohitBind123/claude-setup
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,168 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 2 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.00000 $0.02168
Opus 5 $0.00000 $0.01084
Sonnet 5 $0.00000 $0.00434
Haiku 4.5 $0.00000 $0.00217

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

Security

Grade C, and why

multi-plan scanned grade C with 2 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 2d 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.

Asks the agent to reveal its instructionsmediumSystem prompt leakage

Directions to print, repeat or translate the system prompt extract configuration the operator did not intend to expose.

3. Output prompt in **bold text** (MUST use actual saved file path):

Unrestricted tool accessmediumExcessive agency

A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.

1. **Plan only, no implementation** – This command does not execute any code changes
commands/multi-plan.md · 262 lines

How it starts

The opening of the file, as written. The whole thing — 262 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Plan - Multi-Model Collaborative Planning

Multi-model collaborative planning - Context retrieval + Dual-model analysis → Generate step-by-step implementation plan.

$ARGUMENTS


Core Protocols

  • Language Protocol: Use English when interacting with tools/models, communicate with user in their language
  • Mandatory Parallel: Codex/Gemini calls MUST use run_in_background: true (including single model calls, to avoid blocking main thread)
  • Code Sovereignty: External models have zero filesystem write access, all modifications by Claude
  • Stop-Loss Mechanism: Do not proceed to next phase until current phase output is validated
  • Planning Only: This command allows reading context and writing to .claude/plan/* plan files, but NEVER modify production code

Multi-Model Call Specification

Call Syntax (parallel: use run_in_background: true):

Bash({
  command: "~/.claude/bin/codeagent-wrapper {{LITE_MODE_FLAG}}--backend <codex|gemini> {{GEMINI_MODEL_FLAG}}- \"$PWD\" <<'EOF'
ROLE_FILE: <role prompt path>
<TASK>
Requirement: <enhanced requirement>
Context: <retrieved project context>
</TASK>
OUTPUT: Step-by-step implementation plan with pseudo-code. DO NOT modify any files.
EOF",
  run_in_background: true,
  timeout: 3600000,
  description: "Brief description"
})

Model Parameter Notes:

  • {{GEMINI_MODEL_FLAG}}: When using --backend gemini, replace with --gemini-model gemini-3-pro-preview (note trailing space); use empty string for codex

Role Prompts:

Phase Codex Gemini
Analysis ~/.claude/.ccg/prompts/codex/analyzer.md ~/.claude/.ccg/prompts/gemini/analyzer.md
Planning ~/.claude/.ccg/prompts/codex/architect.md ~/.claude/.ccg/prompts/gemini/architect.md

Session Reuse: Each call returns SESSION_ID: xxx (typically output by wrapper), MUST save for subsequent /ccg:execute use.

Wait for Background Tasks (max timeout 600000ms = 10 minutes):

Read the full file on GitHub · 262 lines

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. 2d ago First seen · 262 lines · 0 tokens per session scan C dadbdfb9f59e

Subscribe to this mod's changes

multi-plan is a command published in the GitHub repository RohitBind123/claude-setup (2 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,168 tokens. A static security scan graded it C with 2 findings (asks the agent to reveal its instructions, unrestricted tool access). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.