status

A command that reads the active plan file and reports the current goal, progress, next unchecked task, and plan location.

In plain words
What is it for?
Checking the status of a feature or project plan.
Why use it?
It shows where work stands without opening the plan file and finding the next task manually.

Command for Claude Code

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/ffroliva/gflow-cli/status
Clone the repo
git clone --depth 1 https://github.com/ffroliva/gflow-cli

Made for: Claude Code.

Per session 18 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 132 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.

ModelPer sessionOnce invoked
Fable 5 $0.00018 $0.00132
Opus 5 $0.00009 $0.00066
Sonnet 5 $0.00004 $0.00026
Haiku 4.5 $0.00002 $0.00013

Measured 2d ago against content hash 4d2239e97e92, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

status 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 2d 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/status.md · 13 lines

What it actually says

/gflow:status [feature] — Current plan state

Read skills/status/SKILL.md and follow the status variant protocol, passing $ARGUMENTS as the optional feature slug.

Do not call Skill(skill="status") — read the file directly.

The skill at skills/status/SKILL.md runs scripts/dev/active_plan.py and returns the full output: plan file path, title, goal, progress (X/N), and next task block.

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. 2d ago First seen · 13 lines · 18 tokens per session scan A 4d2239e97e92

Subscribe to this mod's changes

status is a command published in the GitHub repository ffroliva/gflow-cli (136 stars, last pushed 2d ago), licensed MIT. It adds 18 tokens to every session and 132 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.