help

A command that explains the current state of a feature-development workflow and shows the next steps.

In plain words
What is it for?
Use it to check progress, find the active phase, recover from a blocked workflow, or see how to begin the next feature.
Why use it?
It prevents confusion when a workflow has not started, is waiting for approval, has failed, or is already complete.

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/marcusgoll/spec-flow/help
Clone the repo
git clone --depth 1 https://github.com/marcusgoll/Spec-Flow

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 1,515 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.01515
Opus 5 $0.00009 $0.00758
Sonnet 5 $0.00004 $0.00303
Haiku 4.5 $0.00002 $0.00152

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

Security

Grade A, and why

help 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/core/help.md · 234 lines

How it starts

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

/help — Context-Aware Workflow Guidance (Thin Wrapper)

v2.0 Architecture: This command analyzes state inline for speed, with detailed rendering logic in the help-agent brief.

Active Feature: !ls -td specs/[0-9]*-* 2>/dev/null | head -1 || echo "none"

State Exists: !test -f "$(ls -td specs/[0-9]*-* 2>/dev/null | head -1)/state.yaml" 2>/dev/null && echo "yes" || echo "no"

Six Contexts (mutually exclusive):

  1. no_feature - No specs/ directory, show getting started
  2. no_state - Feature dir exists but state.yaml missing
  3. blocked - Workflow failed, show recovery options
  4. manual_gate - Waiting for approval, show checklist
  5. complete - All phases done, show next feature options
  6. active - In progress, show current phase and next steps

Architecture: Inline analysis for fast response. Agent brief at .claude/agents/phase/help-agent.md contains rendering templates.

Step 1: Detect Context

FEATURE_DIR=$(ls -td specs/[0-9]*-* 2>/dev/null | head -1)

if [ -z "$FEATURE_DIR" ]; then
    CONTEXT="no_feature"
elif [ ! -f "$FEATURE_DIR/state.yaml" ]; then
    CONTEXT="no_state"
else
    STATUS=$(yq eval '.workflow.status' "$FEATURE_DIR/state.yaml" 2>/dev/null || echo "unknown")
    PREVIEW=$(yq eval '.workflow.manual_gates.preview.status' "$FEATURE_DIR/state.yaml" 2>/dev/null || echo "null")
    STAGING=$(yq eval '.workflow.manual_gates.validate_staging.status' "$FEATURE_DIR/state.yaml" 2>/dev/null || echo "null")

    if [ "$STATUS" = "failed" ]; then
        CONTEXT="blocked"
    elif [ "$PREVIEW" = "pending" ] || [ "$STAGING" = "pending" ]; then
        CONTEXT="manual_gate"
    elif [ "$STATUS" = "completed" ]; then
        CONTEXT="complete"
    else
        CONTEXT="active"
    fi
fi

echo "Context: $CONTEXT"
echo "Feature: $FEATURE_DIR"

Step 2: Render Based on Context

Read the full file on GitHub · 234 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. 2d ago First seen · 234 lines · 18 tokens per session scan A aad097d76a2a

Subscribe to this mod's changes

help is a command published in the GitHub repository marcusgoll/Spec-Flow (91 stars, last pushed 4mo ago), licensed MIT. It adds 18 tokens to every session and 1,515 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.