A command that takes an idea for a Git repository through design, implementation planning, and parallel execution. A Git repository is a project whose changes and history are tracked by Git.

Use it to turn a new idea into an approved design and plan, then run the planned work across parallel tasks.

It brings the full workflow into one command while requiring checks and approvals at the stages where decisions are made.

flow — Command by bacsystem

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/bacsystem/parallel-plan-executor/flow

Clone the repo

git clone --depth 1 https://github.com/bacsystem/parallel-plan-executor

Per session 59 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,053 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.

Model	Per session	Once invoked
Fable 5	$0.00059	$0.02053
Opus 5	$0.00030	$0.01026
Sonnet 5	$0.00012	$0.00411
Haiku 4.5	$0.00006	$0.00205

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

Security

Grade A, and why

flow 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.

commands/flow.md · 160 lines

How it starts

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

What this command does

Takes an idea from zero to a running parallel execution: design spec → implementation plan → parallel-plan-executor Workflow, with the user's approval gates at every stage. Invoking /cys:flow IS the choice of parallel execution — never offer sequential alternatives.

REPO = ${CLAUDE_PLUGIN_ROOT}

Steps

Parse $ARGUMENTS: the first whitespace-separated token is repo-path (absolute path of the target repo); everything after it is the idea, free-form. Ask for whichever is missing — never guess.
Sanity-check before designing anything:
- repo-path exists and is a git repo with a clean working tree (git -C <repo-path> status). If dirty, tell the user and stop — the design/plan stages create commits of their own.
- If the repo has no develop branch, ask the user which branch the eventual PR should target before continuing.
Check for leftover state from an interrupted run: check whether <repo-path>/.cys/state.json exists. If it does not, continue normally. If it does, read it and tell the user its planPath and a one-line summary of each task's status, then ask how to proceed — never decide on your own:
- Handle that first: stop here; tell them to use /cys:run-plan pointed at that planPath to resume it before starting a new idea.
- Ignore it and continue: proceed with this new idea. Mention the leftover file will be overwritten once this run's first task settles.
- Delete it and continue: delete <repo-path>/.cys/state.json, then proceed.
Design: invoke the cys:design skill, working against repo-path (explore ITS files, write the spec under ITS docs/cys/specs/), not against the session's cwd. The user approving the written spec is the gate — if they don't approve, stop; nothing launches.

Read the full file on GitHub · 160 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.

yesterday First seen · 160 lines · 0 tokens per session scan A b24ae50c953a

Subscribe to this mod's changes

flow is a command published in the GitHub repository bacsystem/parallel-plan-executor (2 stars, last pushed 1mo ago), licensed MIT. It adds 59 tokens to every session and 2,053 once invoked, about $0.0003 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.

Git and workflow Planning Productivity ai-agents automation claude-code claude-workflow parallel-execution workflow

flow

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

What this command does

Steps

What this file has done since we first saw it

Other commands, from other repositories

pr-address

plan-save

enforce_standards

OPSX: Sync

context

OPSX: Verify