wf-statusline

wf-statusline is a command for coding agents from hesreallyhim/ultracode-workflows. It costs 12 tokens per session (837 once invoked), scanned B, original, MIT.

A command that installs a lightweight workflow progress display in Claude Code's status row. It can show running and completed work counts, elapsed time, and cached phase names when available.

In plain words
What is it for?
Adding project-wide or user-wide progress reporting to Claude Code and merging the required setting into the existing configuration.
Why use it?
It makes workflow progress visible without opening a separate viewer or storing extra workflow data.

Command

Installs and runs on its own, but its text points at files inside its plugin — anything it tells you to read at a ${CLAUDE_PLUGIN_ROOT} path is only there once the plugin is installed. Installing the plugin gets both.

Part of the ultracode-workflows plugin — 1 skill, 7 commands, 1 hook shipped together

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/hesreallyhim/ultracode-workflows/wf-statusline
Clone the repo
git clone --depth 1 https://github.com/hesreallyhim/ultracode-workflows

Or install ultracode-workflows, the plugin that ships this one along with the rest of its 1 skill, 7 commands, 1 hook.

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 wf-statusline

README.md
[![agentmods](https://agentmods.dev/badge/commands/hesreallyhim/ultracode-workflows/wf-statusline.svg)](https://agentmods.dev/commands/hesreallyhim/ultracode-workflows/wf-statusline)
Your own site
<a href="https://agentmods.dev/commands/hesreallyhim/ultracode-workflows/wf-statusline"><img src="https://agentmods.dev/badge/commands/hesreallyhim/ultracode-workflows/wf-statusline.svg" alt="Measured on agentmods" height="20"></a>
Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 837 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. 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.00012 $0.00837
Opus 5 $0.00006 $0.00418
Sonnet 5 $0.00002 $0.00167
Haiku 4.5 $0.00001 $0.00084

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

Security

Grade B, and why

wf-statusline scanned grade B with 1 finding 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 4d 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.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

- **user** → `~/.claude/settings.json` (every project)
plugins/ultracode-workflows/commands/wf-statusline.md · 55 lines

How it starts

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

/wf-statusline

Install the lightweight workflow-progress statusline. It renders observed running/done counts and elapsed time in the always-visible status row. If the richer run viewer has already cached a static phase plan, phase names appear as optional decoration:

⚡ docs-drift-audit · Inventory › Extract › Check › Fix · ●1 ✓8 8m46s
✔ deep-code-review · Scope✓ Review✓5 Verify✓8 Report✓ · 15⚙ 1.2M 4m10s

The script is at ${CLAUDE_PLUGIN_ROOT}/scripts/workflow-statusline.mjs.

Steps

  1. Ask which scope they want, unless $ARGUMENTS already says:

    • project.claude/settings.json in the current project (this repo only)
    • user~/.claude/settings.json (every project)
  2. Wire it up by editing that settings file yourself. Merge into the existing JSON — never overwrite the file, and preserve every other key:

    {
      "statusLine": {
        "type": "command",
        "command": "config_dir=\"${CLAUDE_CONFIG_DIR:-$HOME/.claude}\"; statusline_script=\"$(ls -t \"$config_dir\"/plugins/cache/ultracode-workflows/ultracode-workflows/*/scripts/workflow-statusline.mjs 2>/dev/null | head -n 1)\"; if [ -n \"$statusline_script\" ]; then exec node \"$statusline_script\"; fi",
        "padding": 0,
        "refreshInterval": 5
      }
    }
    

    Write the resolver literally; do not expand its shell variables while editing the JSON. Claude Code installs marketplace plugins in versioned cache directories, so the command selects the most recently written valid copy on every render instead of persisting one version's path. Both marketplace and plugin directory names are exact; only the version directory is allowed to vary.

  3. If a statusLine already exists, don't silently replace it. Show the user the current command and ask whether to replace it. (Composing two is possible — read stdin once, feed both — but only if they ask.)

  4. Verify the installed command renders before declaring success. Read the exact statusLine.command value back from the settings file and feed that command a sample of the JSON Claude Code pipes in. Do not test a different source path instead:

Read the full file on GitHub · 55 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. 4d ago First seen · 55 lines · 12 tokens per session scan B 672570062765

Subscribe to this mod's changes

wf-statusline is a command published in the GitHub repository hesreallyhim/ultracode-workflows (2 stars, last pushed 28d ago), licensed MIT. It adds 12 tokens to every session and 837 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.