agentmods.dev

setup

setup is a command for Claude Code from ilia-pluzhnikov/claude-code-statusline. It costs 20 tokens per session (379 once invoked), scanned A, original, MIT.

A setup command for connecting the Claude Code status line to its configuration. It previews the proposed change, asks for approval, backs up the settings file, and then writes the change if approved.

In plain words
What is it for?
Use it to install or update the status line from the statusline-for-claude-code plugin.
Why use it?
It makes the configuration change reviewable and prevents it from being applied without explicit consent.

Command for Claude Code

Written for Claude Code: ${CLAUDE_PLUGIN_ROOT} variable. Also seen: mentions Claude Code.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the statusline-for-claude-code plugin — 1 command, 1 hook shipped together

not rated 118repo +1 yesterday A scan 20 tokens original MIT

Good fit Use it to install or update the status line from the statusline-for-claude-code plugin.

Compare 6 commands from other repositories ↓
View source ↗ ilia-pluzhnikov/claude-code-statusline
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add ilia-pluzhnikov/claude-code-statusline
Claude Code
/plugin install statusline-for-claude-code

Made for: Claude Code.

Or install statusline-for-claude-code, the plugin that ships this one along with the rest of its 1 command, 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 setup

README.md
[![agentmods](https://agentmods.dev/badge/commands/ilia-pluzhnikov/claude-code-statusline/setup/github.svg)](https://agentmods.dev/commands/ilia-pluzhnikov/claude-code-statusline/setup)
Your own site
<a href="https://agentmods.dev/commands/ilia-pluzhnikov/claude-code-statusline/setup"><img src="https://agentmods.dev/badge/commands/ilia-pluzhnikov/claude-code-statusline/setup/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for setup

Your own site · 80×15
<a href="https://agentmods.dev/commands/ilia-pluzhnikov/claude-code-statusline/setup"><img src="https://agentmods.dev/badge/commands/ilia-pluzhnikov/claude-code-statusline/setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 20 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 379 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00020 $0.00379
Opus 5.5 $0.00008 $0.00152
Sonnet 5.5 $0.00004 $0.00076
Haiku 4.5 $0.00002 $0.00038

Measured 13d ago against content hash cbf914ea4eb7, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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

commands/setup.md · 30 lines

What it actually says

Set up the statusline-for-claude-code plugin's status line. Work through these steps in order. If a command fails, stop and quote its error to the user.

  1. Stage the script by running:

    node "${CLAUDE_PLUGIN_ROOT}/scripts/stage-statusline.js" "${CLAUDE_PLUGIN_ROOT}" "${CLAUDE_PLUGIN_DATA}"

    It prints the path of the staged statusline.js. Use that exact path as SCRIPT in the next steps.

  2. Preview the change by running:

    node "${CLAUDE_PLUGIN_ROOT}/scripts/configure-statusline.js" plan "SCRIPT"

    It writes nothing and prints JSON with settingsPath, current, proposed and isAlreadySet.

    • If isAlreadySet is true, tell the user the status line is already set up, and stop.
    • Otherwise show the user settingsPath, the current statusLine (or say there is none) and the proposed one. Say that applying replaces only the statusLine key and first backs the file up to settings.json.bak.

  3. Ask the user whether to apply the change, and wait for an explicit yes. On any other answer, stop without writing anything.

  4. Apply the change by running:

    node "${CLAUDE_PLUGIN_ROOT}/scripts/configure-statusline.js" apply "SCRIPT"

    Report settingsPath and backupPath from its output.

  5. Tell the user that the status line appears on Claude Code's next refresh (restart Claude Code if it doesn't), that plugin updates reach it without running setup again, and that restoring settings.json.bak undoes the change.

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. 13d ago First seen · 30 lines · 20 tokens per session scan A cbf914ea4eb7

Subscribe to this mod's changes

setup is a command published in the GitHub repository ilia-pluzhnikov/claude-code-statusline (118 stars, last pushed yesterday), licensed MIT. It adds 20 tokens to every session and 379 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-03.

Claude CodeProductivityanthropicclaudedotfilesnodejsstatusline
Related

Other commands, from other repositories

cleanup

Sweep /.claude disk hygiene to stated retentions, clean up stale plans from repos, audit plugin health, and compact agent memory files.

w2ur/claude-code-setup · 28 tokens

claudetower:widgets

A ClaudeTower command for turning status-line widgets on or off, such as the model, project location, Git state, context use, cost, usage limits, and active account.

sodam-ai/ClaudeTower · 47 tokens

claudetower:config

A ClaudeTower configuration command for changing the status line's refresh interval, separators, and left and right spacing.

sodam-ai/ClaudeTower · 33 tokens

claudetower:status

A status command for ClaudeTower, a command-line tool that adds information to a coding assistant's status line.

sodam-ai/ClaudeTower · 33 tokens

rename

Generate a concise, sentence-case title (3-7 words) that captures the main topic or goal of this coding session. The title should be clear enough that the user recognizes the session in a list. Use sentence case: capitalize only the first word and proper nouns.

asgeirtj/system_prompts_leaks · 0 tokens

obsidian-recap

Summarize a time period from the vault - today, week, or month.

eugeniughelbur/obsidian-second-brain · 16 tokens