plan-workflow

plan-workflow is a command for Claude Code from organvm-iv-taxis/a-i--skills. It costs 24 tokens per session (303 once invoked), scanned A, original, Apache-2.0.

A command that plans a sequence of reusable agent skills for completing a large development task.

In plain words
What is it for?
Use it to design workflows such as planning an API, writing its backend, adding tests, and preparing deployment.
Why use it?
It helps break a broad goal into compatible steps and shows what each step needs and produces before work begins.

Command for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the example-skills plugin — 47 skills, 2 commands, 1 agent shipped together

Good fit Use it to design workflows such as planning an API, writing its backend, adding tests, and preparing deployment.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/organvm-iv-taxis/a-i--skills/plan-workflow
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.

Clone the repo
git clone --depth 1 https://github.com/organvm-iv-taxis/a-i--skills

Made for: Claude Code.

Or install example-skills, the plugin that ships this one along with the rest of its 47 skills, 2 commands, 1 agent.

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 plan-workflow

README.md
[![agentmods](https://agentmods.dev/badge/commands/organvm-iv-taxis/a-i--skills/plan-workflow/github.svg)](https://agentmods.dev/commands/organvm-iv-taxis/a-i--skills/plan-workflow)
Your own site
<a href="https://agentmods.dev/commands/organvm-iv-taxis/a-i--skills/plan-workflow"><img src="https://agentmods.dev/badge/commands/organvm-iv-taxis/a-i--skills/plan-workflow/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for plan-workflow

Your own site · 80×15
<a href="https://agentmods.dev/commands/organvm-iv-taxis/a-i--skills/plan-workflow"><img src="https://agentmods.dev/badge/commands/organvm-iv-taxis/a-i--skills/plan-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 24 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 303 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00024 $0.00303
Opus 5 $0.00012 $0.00151
Sonnet 5 $0.00005 $0.00061
Haiku 4.5 $0.00002 $0.00030

Measured 11d ago against content hash 3a689b260a71, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

plan-workflow 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 11d 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.

commands/plan-workflow.md · 53 lines

What it actually says

/plan-workflow

Generate an ordered skill chain to accomplish a goal.

Usage

/plan-workflow <goal description>

Example: /plan-workflow Build a secure REST API with tests and deployment

Process

  1. Read distributions/skills-registry.json to load all skill metadata
  2. Match the goal against skill descriptions, tags, and triggers
  3. Build a dependency chain based on input/output compatibility
  4. Include complementary skills that enhance the workflow
  5. Present the plan as an ordered list with data flow

Output Format

Goal: <user's goal>

Skill Chain:
1. skill-name (category)
   Inputs: what it needs
   Outputs: what it produces
   Purpose: why it's in the chain

2. skill-name (category)
   ...

Data Flow:
  service-requirements -> [api-design-patterns] -> api-specification
  api-specification -> [backend-implementation-patterns] -> backend-code
  ...

Also Consider:
  - complementary-skill: brief description

Notes

  • Plans are suggestions; approve or modify before executing
  • Use /skill-health to check individual skills before running a chain
  • Chains are limited to 8 skills for reviewability
  • Prefer core-tier skills when multiple options match
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. 11d ago First seen · 53 lines · 24 tokens per session scan A 3a689b260a71

Subscribe to this mod's changes

plan-workflow is a command published in the GitHub repository organvm-iv-taxis/a-i--skills (17 stars, last pushed 14d ago), licensed Apache-2.0. It adds 24 tokens to every session and 303 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-08-30.