flow

flow is a command for Claude Code from hgahlot/claude-flow. It costs 0 tokens per session (3,509 once invoked), scanned C, original, MIT.

A single command that guides a project through stages from deciding what to build to deployment and monitoring.

In plain words
What is it for?
Use it to route a request to the appropriate command for planning, building, testing, reviewing, accepting, shipping, deploying, or monitoring.
Why use it?
It helps you choose the next development action without remembering several separate command systems.

Command for Claude Code

Written for Claude Code: PreToolUse hook event. Also seen: mentions subagents; mentions Claude Code; built for gstack.

Good fit Use it to route a request to the appropriate command for planning, building, testing, reviewing, accepting, shipping, deploying, or monitoring.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/hgahlot/claude-flow/flow
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/hgahlot/claude-flow

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 flow

README.md
[![agentmods](https://agentmods.dev/badge/commands/hgahlot/claude-flow/flow/github.svg)](https://agentmods.dev/commands/hgahlot/claude-flow/flow)
Your own site
<a href="https://agentmods.dev/commands/hgahlot/claude-flow/flow"><img src="https://agentmods.dev/badge/commands/hgahlot/claude-flow/flow/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 flow

Your own site · 80×15
<a href="https://agentmods.dev/commands/hgahlot/claude-flow/flow"><img src="https://agentmods.dev/badge/commands/hgahlot/claude-flow/flow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
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 3,509 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. 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.00000 $0.03509
Opus 5.5 $0.00000 $0.01404
Sonnet 5.5 $0.00000 $0.00702
Haiku 4.5 $0.00000 $0.00351

Measured 2mo ago against content hash afe7a6d4a5fa, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade C, and why

flow scanned grade C with 1 finding 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 2mo 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

> PreToolUse hook: blocks rm -rf, DROP TABLE, force push automatically.
commands/flow.md · 547 lines

How it starts

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

You are the unified development flow guide for this project. You are the ONLY command the user needs to remember. Everything — GSD, gstack, Superpowers, all of it — routes through you.

Your job: read what the user wants to do, find the right command, and present it clearly. Never say "use GSD" or "use gstack" — just say "run /command".


How to respond

  1. Read STATE.md to understand current project state and phase.
  2. If the user passed a stage argument (e.g. /flow build, /flow ship), jump directly to that section.
  3. If no argument, check STATE.md and show the logical next step.
  4. If the user described a situation in natural language, find it in the routing table below and show the matching section.
  5. Always end with: "Ready to run this? I can kick it off for you."

Show each command like this:

/command-name

What it does in one sentence. Then 2–3 bullet points of what actually happens.


THE PIPELINE

Always show this header so the user knows where they are:

THINK → DESIGN → INIT → [ PLAN → BUILD → TEST → REVIEW → ACCEPT ] → SHIP → DEPLOY → MONITOR
                          └────────────── repeat per feature ───────────────┘

STAGE: THINK

Starting something new and want to validate the idea first

/ce:ideate

Discover high-impact improvements through divergent ideation and adversarial filtering.

  • Generates grounded ideas based on your actual codebase
  • Critically evaluates each idea before presenting
  • Use when you need inspiration for what to build next
/office-hours

YC-style product forcing questions before writing a line of code.

  • Asks 6 forcing questions, researches competitors, surfaces riskiest assumptions
  • Produces a design doc with problem/solution/differentiation
  • Use for pure product/business validation

STAGE: DESIGN

Need to lock in the visual or system design before building

/design-consultation

Builds a complete DESIGN.md + HTML preview.

  • Pattern database activates automatically: 67 styles, 96 palettes, stack-specific patterns
  • For a scoped UI phase (not full product design), use /gsd:ui-phase instead

Read the full file on GitHub · 547 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. 2mo ago First seen · 547 lines · 0 tokens per session scan C afe7a6d4a5fa

Subscribe to this mod's changes

flow is a command published in the GitHub repository hgahlot/claude-flow (55 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,509 tokens. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

flow compared with commands from other repositories

flow next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
flowhgahlot/claude-flowCommand557mo agoMITC0Claude Code
cost-optimizewshobson/agentsCommand42kyesterdayMITA26Claude Code
deploybutterbase-ai/butterbase-skillsCommand5356d agoMITA20Claude Code
envvercel/vercel-pluginCommand326yesterdaynoneA35Claude Code
firebase-publishPierry/harness-kitCommand41mo agoMITA20Claude Code
scanprajapatimehul/claude-aws-cost-saverCommand244mo agoMITA6Claude Code
migrationdatabayt/hogwartsCommand183d agononeA4Claude Code