plan-status

plan-status is a command for Claude Code from Langerrr/zforge. It costs 8 tokens per session (414 once invoked), scanned A, original, MIT.

A workspace report that finds feature plans and shows their progress, completion state, and unresolved flags.

In plain words
What is it for?
Use it to review all feature plans under the current folder and list open standing flags, which are issues carried between work sessions.
Why use it?
It avoids opening each plan separately to discover what is finished, running, pending, or still needs attention.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: model in frontmatter.

Part of the zforge plugin — 13 skills, 8 commands, 2 agents shipped together

Good fit Use it to review all feature plans under the current folder and list open standing flags, which are issues carried between work sessions.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/langerrr/zforge/plan-status
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/Langerrr/zforge

Made for: Claude Code.

Or install zforge, the plugin that ships this one along with the rest of its 13 skills, 8 commands, 2 agents.

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-status

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

Your own site · 80×15
<a href="https://agentmods.dev/commands/langerrr/zforge/plan-status"><img src="https://agentmods.dev/badge/commands/langerrr/zforge/plan-status.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 8 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 414 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.00008 $0.00414
Opus 5.5 $0.00003 $0.00166
Sonnet 5.5 $0.00002 $0.00083
Haiku 4.5 $0.00001 $0.00041

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

Security

Grade A, and why

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

commands/plan-status.md · 41 lines

What it actually says

/plan-status — Workspace Feature Status

Scan for all feature plans under the current working directory and display their status.

Process

  1. Search for all 05_progress_overview.md files under the current working directory using Glob: **/docs/*/05_progress_overview.md

  2. For each found file:

    • Extract the feature name from the directory path
    • Read the file and parse the phase summary table and the Standing Flags section
    • Count: total phases, completed, running, pending, and open standing flags
  3. Display a summary table:

Feature Plans in {current_directory}:

  Feature              Status       Progress    Flags   Path
  ────────────────────────────────────────────────────────────────
  ai_assistant         In Progress  3/5 phases  —       docs/ai_assistant/
  video_pipeline       In Progress  1/3 phases  1 open  docs/video_pipeline/
  api_refactor         Complete     2/2 phases  —       docs/api_refactor/

A feature with every phase complete and an open standing flag is not Complete. Show it as Flagged with the flag count — the whole point of tracking flags is that they survive the run ending.

  1. List open standing flags below the table, with the phase that opened each, its kind, and what closes it. Name the OUTWARD ones first: an inward flag is a gap this feature can still close, and an OUTWARD one is an obligation waiting on a planner who has not read the feature that found it.

  2. If no 05_progress_overview.md files are found, report: "No feature plans found under {current_directory}."

Scope

ONLY look under the current working directory. Do not search parent directories or sibling projects.

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 Changed 34f793d52c90
  2. 2mo ago First seen · 41 lines · 8 tokens per session scan A 80c0599c039d

Subscribe to this mod's changes

plan-status is a command published in the GitHub repository Langerrr/zforge (12 stars, last pushed 1mo ago), licensed MIT. It adds 8 tokens to every session and 414 once invoked, about $0.0000 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-31.