setup

A setup command that registers the claude-statusline tool in Claude Code's settings file.

In plain words
What is it for?
Use it when installing claude-statusline for the first time or enabling it in a Claude Code project.
Why use it?
It removes the need to edit the settings file by hand. Claude Code must be restarted after setup for the status line to appear.

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/bouob/claude-statusline/setup
Clone the repo
git clone --depth 1 https://github.com/bouob/claude-statusline
Per session 15 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 73 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.00015 $0.00073
Opus 5 $0.00008 $0.00036
Sonnet 5 $0.00003 $0.00015
Haiku 4.5 $0.00002 $0.00007

Measured yesterday against content hash 059973a14925, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade B, and why

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

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.

description: Set up claude-statusline by registering it in ~/.claude/settings.json
commands/setup.md · 13 lines

What it actually says

Run the setup script to register claude-statusline:

node "${CLAUDE_PLUGIN_ROOT}/scripts/setup.js"

After the script completes, tell the user to restart Claude Code for the statusline to take effect.

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. yesterday First seen · 13 lines · 15 tokens per session scan B 059973a14925

Subscribe to this mod's changes

setup is a command published in the GitHub repository bouob/claude-statusline (2 stars, last pushed 1mo ago), licensed MIT. It adds 15 tokens to every session and 73 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.