add-statusline

add-statusline is a command for coding agents from barkain/claude-code-workflow-orchestration. It costs 8 tokens per session (404 once invoked), scanned B, original, MIT.

A command that adds a status line to a Claude settings file. The status line is text shown while Claude Code is running.

In plain words
What is it for?
Use it to configure the status line in your user, project, or local Claude settings.
Why use it?
It avoids manually editing JSON settings and handles updating an existing file or creating a new one.

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 workflow-orchestrator plugin — 2 commands, 8 agents 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/barkain/claude-code-workflow-orchestration/add-statusline
Clone the repo
git clone --depth 1 https://github.com/barkain/claude-code-workflow-orchestration

Or install workflow-orchestrator, the plugin that ships this one along with the rest of its 2 commands, 8 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 add-statusline

README.md
[![agentmods](https://agentmods.dev/badge/commands/barkain/claude-code-workflow-orchestration/add-statusline.svg)](https://agentmods.dev/commands/barkain/claude-code-workflow-orchestration/add-statusline)
Your own site
<a href="https://agentmods.dev/commands/barkain/claude-code-workflow-orchestration/add-statusline"><img src="https://agentmods.dev/badge/commands/barkain/claude-code-workflow-orchestration/add-statusline.svg" alt="Measured on agentmods" 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 404 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.00008 $0.00404
Opus 5 $0.00004 $0.00202
Sonnet 5 $0.00002 $0.00081
Haiku 4.5 $0.00001 $0.00040

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

Security

Grade B, and why

add-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 5d 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`
commands/add-statusline.md · 63 lines

What it actually says

Add StatusLine Configuration

Adds the statusline configuration to a Claude settings file.

Step 1: Ask Scope

Use AskUserQuestion to ask which settings file:

  • user: ~/.claude/settings.json
  • project: ./.claude/settings.json
  • local: ./.claude/settings.local.json

Step 2: Execute via Agent

Spawn a general-purpose subagent with the Agent tool:

Agent(
  subagent_type: "general-purpose",
  description: "Add statusline to settings",
  prompt: "Add statusline configuration to [FILE_PATH].

Use the Read tool to check if file exists. Then:

IF FILE EXISTS:
1. Parse existing JSON
2. Add/merge statusLine key
3. Use Edit tool to update

IF FILE DOES NOT EXIST:
1. Create parent directory if needed: mkdir -p [PARENT_DIR]
2. Use Write tool to create file with this content:
{
  \"statusLine\": {
    \"type\": \"command\",
    \"command\": \"uv run --no-project --script ${CLAUDE_PLUGIN_ROOT}/scripts/statusline.py\",
    \"padding\": 0
  }
}
3. Report CREATED

statusLine value to add:
{
  \"type\": \"command\",
  \"command\": \"uv run --no-project --script ${CLAUDE_PLUGIN_ROOT}/scripts/statusline.py\",
  \"padding\": 0
}

Respond SUCCESS (updated) or CREATED (new file)."
)

Step 3: Handle Response

  • CREATED: Inform user the settings file was created and statusline was added.
  • INVALID_JSON: Show error details. Exit.
  • SUCCESS: Confirm the statusline configuration was successfully added.
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. 5d ago First seen · 63 lines · 8 tokens per session scan B dc0e61c5ebd2

Subscribe to this mod's changes

add-statusline is a command published in the GitHub repository barkain/claude-code-workflow-orchestration (84 stars, last pushed 1mo ago), licensed MIT. It adds 8 tokens to every session and 404 once invoked, about $0.0000 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-30.