workflow-status

A lightweight command that reads a YAML workflow-status file and reports what an agent should do next.

In plain words
What is it for?
Use it during an existing workflow to check progress and decide the next action; use workflow-init when starting a new project.
Why use it?
It makes the current project step visible without performing a full project setup.

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/terryso/autoqa-agent/workflow-status
Clone the repo
git clone --depth 1 https://github.com/terryso/AutoQA-Agent

Made for: Claude Code.

Per session 33 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 189 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 78% copy Near-identical to another mod 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.00033 $0.00189
Opus 5 $0.00016 $0.00095
Sonnet 5 $0.00007 $0.00038
Haiku 4.5 $0.00003 $0.00019

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

Security

Grade A, and why

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

Origin

This is a copy

78% identical to correct-course — 6 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/commands/bmad/bmm/workflows/workflow-status.md · 14 lines

What it actually says

IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:

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 · 14 lines · 33 tokens per session scan A 7d243cdb2526

Subscribe to this mod's changes

workflow-status is a command published in the GitHub repository terryso/AutoQA-Agent (134 stars, last pushed 7mo ago), licensed MIT. It adds 33 tokens to every session and 189 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 78% identical to correct-course, differing in 6 lines, and is treated as a copy.