gflow-cli: Command for Claude Code

.claude/commands/gflow/plan.md

plan is a command for Claude Code from ffroliva/gflow-cli. It costs 22 tokens per session (260 once invoked), scanned A, original, MIT.

A command that turns a feature idea into a written, step-by-step implementation plan. It records the plan in the project’s documentation folder.

In plain words
What is it for?
Use it to plan coding work, identify edge cases, and create checklists before implementation.
Why use it?
It breaks a large feature into small tasks that can be implemented and tested one at a time.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

This is ffroliva/gflow-cli's own configuration. It tells Claude Code how to work on gflow-cli itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything gflow-cli configures →

Reuse

Borrowing it

Nothing to install: this file belongs to ffroliva/gflow-cli. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/ffroliva/gflow-cli/develop/.claude/commands/gflow/plan.md
Clone the repo
git clone --depth 1 https://github.com/ffroliva/gflow-cli

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 plan

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

Your own site · 80×15
<a href="https://agentmods.dev/commands/ffroliva/gflow-cli/plan"><img src="https://agentmods.dev/badge/commands/ffroliva/gflow-cli/plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 22 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 260 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.00022 $0.00260
Opus 5.5 $0.00009 $0.00104
Sonnet 5.5 $0.00004 $0.00052
Haiku 4.5 $0.00002 $0.00026

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

Security

Grade A, and why

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 1mo 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.

.claude/commands/gflow/plan.md · 23 lines

What it actually says

/gflow:plan <feature> — Create a feature plan

Read skills/plan/SKILL.md and follow its protocol now, passing $ARGUMENTS as the feature description.

Do not call Skill(skill="plan") — the repo's skills/*/SKILL.md files are plain Markdown, not registered as Skill-tool-invocable. Read the file directly instead.

The skill at skills/plan/SKILL.md gathers predict/scenario context, asks ≤3 clarifying questions, decomposes the feature into atomic committable tasks with step + test checklists, and writes docs/superpowers/plans/<date>-<slug>/PLAN.md.

Typical workflow:

/gflow:predict <proposal>   →  GO / CAUTION / STOP
/gflow:scenario <feature>   →  edge cases + BDD skeleton
/gflow:plan <feature>       →  writes PLAN.md  ← this command
/gflow:status               →  surfaces next task
/gflow:check                →  before each commit
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. 1mo ago First seen · 23 lines · 22 tokens per session scan A 7f53cf0760d5

Subscribe to this mod's changes

plan is a command published in the GitHub repository ffroliva/gflow-cli (337 stars, last pushed yesterday), licensed MIT. It adds 22 tokens to every session and 260 once invoked, about $0.0001 per session on Opus 5.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.