A command that reports the current state of a SoloFlow project workflow. SoloFlow stores plans, sprints, checkpoints, reviews, and completed tasks in project files.

Checking whether SoloFlow is initialized, counting ready and completed work, reviewing active sprints, and seeing pending human reviews or follow-up items.

It gathers progress from several files and turns it into one status report. If the project has not been initialized, it tells you what setup command is needed.

status — Command by kesteva

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/kesteva/soloflow/status

Clone the repo

git clone --depth 1 https://github.com/kesteva/soloflow

Per session 9 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 558 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.00009	$0.00558
Opus 5	$0.00005	$0.00279
Sonnet 5	$0.00002	$0.00112
Haiku 4.5	$0.00001	$0.00056

Measured 2d ago against content hash d1f8afb6ee76, 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.

commands/status.md · 57 lines

What it actually says

/soloflow:status

Display the current SoloFlow workflow state for this project.

Steps

Check initialization. If .soloflow/ does not exist, report: "SoloFlow not initialized. Run /soloflow:init first." and stop.
Read state files:
- Plans under .soloflow/active/plans/**/TASK-*-plan.md — frontmatter status is the queue source of truth (use node "${CLAUDE_PLUGIN_ROOT}/scripts/state/plan-query.js" --status ready for ready count, etc.)
- .soloflow/active/sprints/*/sprint.json (per-sprint layout; glob across all active sprints)
- .soloflow/checkpoint.md for last checkpoint info
- .soloflow/human-review-queue.md for pending reviews
Count archive files:
- Count .md files in .soloflow/archive/done/ for completed tasks
- Count .md files in .soloflow/archive/compound/ for compound proposals

3.5. Resolve queue bucket counts. Run node "${CLAUDE_PLUGIN_ROOT}/scripts/state/review-queue.js" gather and read buckets.{decisions,actions,testing,deferred_visual} from the JSON output (plus pending_count for the total). If the queue file does not exist, treat all counts as 0.

Display the report:

## SoloFlow Status

### Sprint
- **ID:** {sprint ID or "No active sprint"}
- **Status:** {active / complete / none}
- **Started:** {timestamp or "—"}

### Active Tasks
- **Ready:** {count}
- **In progress:** {count}
- **Blocked:** {count}
- **Stuck:** {count}
- **Human-needed:** {count}

### Archive
- **Completed:** {count from archive/done/}
- **Sprints compounded:** {count from archive/compound/}

### Human Review Queue
- **Pending:** {count or "Empty"}
- **Buckets:** Decisions {N} · Actions {N} · Testing {N} · Deferred Visual {N}

### Last Checkpoint
- **Updated:** {timestamp or "No checkpoint"}
- **Next action:** {from checkpoint frontmatter or "—"}

If there are stuck tasks, list them with their task IDs. If there are human-needed tasks, list them too.

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.

2d ago First seen · 57 lines · 9 tokens per session scan A d1f8afb6ee76

Subscribe to this mod's changes

status is a command published in the GitHub repository kesteva/soloflow (40 stars, last pushed 3mo ago), licensed MIT. It adds 9 tokens to every session and 558 once invoked, about $0.0000 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.

Planning Productivity Project management

status

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

/soloflow:status

Steps

What this file has done since we first saw it

Other commands, from other repositories

template

project-recap

speckit.taskstoissues

ado-pull

issue-amend

dispatch-worker