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/catlog22/claude-code-workflow/workflow-multi-cli-plannpx skills add catlog22/Claude-Code-Workflow --skill workflow-multi-cli-plangit clone --depth 1 https://github.com/catlog22/Claude-Code-WorkflowWrote 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/catlog22/claude-code-workflow/workflow-multi-cli-plan)<a href="https://agentmods.dev/skills/catlog22/claude-code-workflow/workflow-multi-cli-plan"><img src="https://agentmods.dev/badge/skills/catlog22/claude-code-workflow/workflow-multi-cli-plan.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.00027 | $0.03772 |
| Opus 5 | $0.00014 | $0.01886 |
| Sonnet 5 | $0.00005 | $0.00754 |
| Haiku 4.5 | $0.00003 | $0.00377 |
Grade A, and why
workflow-multi-cli-plan 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 yesterday.
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 — 425 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Multi-CLI Collaborative Planning
Auto Mode
When workflowPreferences.autoYes is true: Auto-approve plan, use recommended solution and execution method (Agent, Skip review).
Context Source: ACE semantic search + Multi-CLI analysis
Output Directory: .workflow/.multi-cli-plan/{session-id}/
Default Max Rounds: 3 (convergence may complete earlier)
CLI Tools: @cli-discuss-agent (analysis), @cli-lite-planning-agent (plan generation)
Execution: Auto-hands off to workflow-lite-execute after plan approval
Orchestrator Boundary (CRITICAL)
- ONLY command for multi-CLI collaborative planning
- Manages: Session state, user decisions, agent delegation, phase transitions
- Delegates: CLI execution to @cli-discuss-agent, plan generation to @cli-lite-planning-agent
Execution Flow
Phase 1: Context Gathering
└─ ACE semantic search, extract keywords, build context package
Phase 2: Multi-CLI Discussion (Iterative, via @cli-discuss-agent)
├─ Round N: Agent executes Gemini + Codex + Claude
├─ Cross-verify findings, synthesize solutions
├─ Write synthesis.json to rounds/{N}/
└─ Loop until convergence or max rounds
Phase 3: Present Options
└─ Display solutions with trade-offs from agent output
Phase 4: User Decision
├─ Select solution approach
├─ Select execution method (Agent/Codex/Auto)
├─ Select code review tool (Skip/Gemini/Codex/Agent)
└─ Route:
├─ Approve → Phase 5
├─ Need More Analysis → Return to Phase 2
└─ Cancel → Save session
Phase 5: Plan Generation & Execution Handoff
├─ Generate plan.json + .task/*.json (via @cli-lite-planning-agent, two-layer output)
├─ Build executionContext with user selections and taskFiles
└─ Execute via workflow-lite-execute
Agent Roles
| Agent | Responsibility |
|---|---|
| Orchestrator | Session management, ACE context, user decisions, phase transitions, executionContext assembly |
| @cli-discuss-agent | Multi-CLI execution (Gemini/Codex/Claude), cross-verification, solution synthesis, synthesis.json output |
| @cli-lite-planning-agent | Task decomposition, two-layer output: plan.json (overview with task_ids[]) + .task/*.json (task files) |
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.
- yesterday First seen · 425 lines · 27 tokens per session scan A c05ce0e8c535
workflow-multi-cli-plan is a skill published in the GitHub repository catlog22/Claude-Code-Workflow (2,133 stars, last pushed 2mo ago), licensed MIT. It adds 27 tokens to every session and 3,772 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
alive:create-walnut
Something new is emerging. A venture, an experiment, a person entering the orbit, a life area getting serious. It needs its own walnut — its own identity, history, and future. Scaffolds the full structure, maps existing context sources, and optionally migrates files across.
alive-create
Scaffold a new walnut -- venture, experiment, person, life area, project.
alive-project
Regenerate now.json projections for all walnuts (mechanical, no approval needed).
artifact-management
Use for PACEflow artifact fields and formats: task indexes, CHG/HOTFIX lifecycle operations, artifact-writer prompts, approvals, verification, and archive.
doc-todo-log-loop
基于日志记录驱动的轻量级项目开发和管理方案，是新项目的缺省管理方案.
pace-bridge
Use to bridge a confirmed Superpowers/native plan into PACEflow CHG/HOTFIX artifacts, create artifact-writer prompts, and mark the specific plan as synced.