setup-statusline

An interactive wizard for configuring the status line shown in Claude Code. It creates a script that can display your folder, Git branch and changes, token usage, colors, and your last message.

In plain words
What is it for?
Use it when you want Claude Code to show project location, Git status, context-window usage, or the last prompt while you work.
Why use it?
It avoids manually writing or editing a status-line script. The wizard collects your preferences in one setup flow.

Command

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/bvdr/claude-plugins/setup-statusline
Clone the repo
git clone --depth 1 https://github.com/bvdr/claude-plugins
Per session 36 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,722 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.00036 $0.02722
Opus 5 $0.00018 $0.01361
Sonnet 5 $0.00007 $0.00544
Haiku 4.5 $0.00004 $0.00272

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

Security

Grade B, and why

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

Reads agent configuration directoriesmediumAgent snooping

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

- Otherwise → `~/.claude/settings.json`
plugins/bvdr/commands/setup-statusline.md · 341 lines

How it starts

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

Statusline Setup Wizard

This skill walks you through configuring a custom Claude Code statusline with interactive questions.

What Gets Configured

  • Folder display: Show/hide, full path vs last folder(s)
  • Git branch info: Uncommitted files, sync status
  • Context bar: Token usage visualization
  • Color theme: Choose accent color
  • Last message: Second line showing your last prompt

Example Output

📁myproject | 🔀main (2 files uncommitted, synced) | [███░░░░░░░] 15% of 200k tokens used
💬 Can you check if the edd license plugin is enabled...

Configuration Flow

When this skill is invoked, use the AskUserQuestion tool to gather preferences. Ask all questions in a SINGLE AskUserQuestion call with multiple questions.

Questions to Ask

Use AskUserQuestion with these 4 questions:

{
  "questions": [
    {
      "question": "How should the folder name be displayed?",
      "header": "Folder",
      "options": [
        {"label": "Last folder only (Recommended)", "description": "Shows just 'myproject' - clean and minimal"},
        {"label": "Last 2 folders", "description": "Shows 'Sites/myproject' - more context"},
        {"label": "Full path", "description": "Shows '/Users/you/Sites/myproject' - complete path"},
        {"label": "Don't show folder", "description": "Hide folder from statusline"}
      ],
      "multiSelect": false
    },
    {
      "question": "What accent color would you like for the statusline?",
      "header": "Color",
      "options": [
        {"label": "Blue (Recommended)", "description": "Clean, professional look"},
        {"label": "Orange", "description": "Warm, energetic feel"},
        {"label": "Green", "description": "Natural, calming tone"},
        {"label": "Gray", "description": "Minimal, monochrome style"}
      ],
      "multiSelect": false
    },
    {
      "question": "Show git branch with status info?",
      "header": "Git",
      "options": [
        {"label": "Yes with full status (Recommended)", "description": "Branch + uncommitted count + sync status"},
        {"label": "Branch name only", "description": "Just the branch name, no extra info"},
        {"label": "No git info", "description": "Hide git information completely"}
      ],
      "multiSelect": false
    },
    {
      "question": "Show your last message on a second line?",
      "header": "Last msg",
      "options": [
        {"label": "Yes (Recommended)", "description": "Shows 💬 with your last prompt - helps identify conversations"},
        {"label": "No", "description": "Single line statusline only"}
      ],
      "multiSelect": false
    }
  ]
}

Read the full file on GitHub · 341 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 · 341 lines · 36 tokens per session scan B 573244bf13d2

Subscribe to this mod's changes

setup-statusline is a command published in the GitHub repository bvdr/claude-plugins (3 stars, last pushed 2mo ago), licensed MIT. It adds 36 tokens to every session and 2,722 once invoked, about $0.0002 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.