agentmods.dev

statusline-setup

statusline-setup is a command for Claude Code from ShivaeDev/pardes. It costs 52 tokens per session (422 once invoked), scanned B, original, MIT.

A command that connects Claude Code’s main status line to the statusline@pardes plugin.

In plain words
What is it for?
It refreshes the launcher, updates Claude Code’s settings when allowed, and reports whether the plugin was wired or the existing custom setting was left unchanged.
Why use it?
It provides an on-demand way to install or refresh the status-line launcher while preserving a custom status line already configured by the user.

Command for Claude Code

Written for Claude Code: user-invocable in frontmatter. Also seen: reads .claude/ paths; mentions subagents; 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 plugin — 1 command, 1 hook shipped together

not rated 5repo 3mo ago B scan 52 tokens original MIT

Good fit It refreshes the launcher, updates Claude Code’s settings when allowed, and reports whether the plugin was wired or the existing custom setting was left unchanged.

Compare 6 commands from other repositories ↓
View source ↗ ShivaeDev/pardes
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 ShivaeDev/pardes
Claude Code
/plugin install statusline

Made for: Claude Code.

Or install statusline, 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 statusline-setup

README.md
[![agentmods](https://agentmods.dev/badge/commands/shivaedev/pardes/statusline-setup/github.svg)](https://agentmods.dev/commands/shivaedev/pardes/statusline-setup)
Your own site
<a href="https://agentmods.dev/commands/shivaedev/pardes/statusline-setup"><img src="https://agentmods.dev/badge/commands/shivaedev/pardes/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 statusline-setup

Your own site · 80×15
<a href="https://agentmods.dev/commands/shivaedev/pardes/statusline-setup"><img src="https://agentmods.dev/badge/commands/shivaedev/pardes/statusline-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 52 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 422 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. 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.00052 $0.00422
Opus 5.5 $0.00021 $0.00169
Sonnet 5.5 $0.00010 $0.00084
Haiku 4.5 $0.00005 $0.00042

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

Security

Grade B, and why

statusline-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 2mo 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.

Run the plugin's setup in force mode. This refreshes the stable launcher at `~/.claude/statusline-pardes.sh` so it points at the current plugin source, then points `~/.claude/settings.json`'s `statusLine` at that launche
plugins/statusline/commands/statusline-setup.md · 29 lines

What it actually says

statusline-setup

Explicitly install or refresh the main status line for the statusline plugin.

The subagent status line is wired automatically (it ships in the plugin's bundled settings.json). The main line cannot be set declaratively by a plugin, so it is wired by a SessionStart hook — and by this command, for an on-demand (re)install.

What to do

Run the plugin's setup in force mode. This refreshes the stable launcher at ~/.claude/statusline-pardes.sh so it points at the current plugin source, then points ~/.claude/settings.json's statusLine at that launcher:

STATUSLINE_PARDES_FORCE=1 "${CLAUDE_PLUGIN_ROOT}/hooks/session-start.sh"

Then report the outcome to the user based on what the script printed:

  • Wired / refreshed — the main status line now renders via this plugin. Tell the user it is active. It takes effect on the next status-line refresh; a new session guarantees it.
  • Custom status line left untouched — the user already has their own statusLine command in settings.json. The plugin will NOT overwrite it. To switch, tell the user to remove the existing statusLine key from ~/.claude/settings.json, then run /statusline-setup again.

How to revert

Tell the user they can remove the wiring at any time by deleting the "statusLine" key from ~/.claude/settings.json. The launcher file ~/.claude/statusline-pardes.sh is harmless to leave or delete; it is recreated whenever the plugin is active and a session starts.

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. 2mo ago First seen · 29 lines · 52 tokens per session scan B e34a7ebb5943

Subscribe to this mod's changes

statusline-setup is a command published in the GitHub repository ShivaeDev/pardes (5 stars, last pushed 3mo ago), licensed MIT. It adds 52 tokens to every session and 422 once invoked, about $0.0002 per session on Opus 5.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.

Related

Other commands, from other repositories

checklist

Generate a custom checklist for the current feature based on user requirements.

github/spec-kit · 13 tokens

clarify

Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.

github/spec-kit · 27 tokens

specify

Create or update the feature specification from a natural language feature description.

github/spec-kit · 13 tokens

converge

Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.

github/spec-kit · 35 tokens

implement

Execute the implementation plan by processing and executing all tasks defined in tasks.md.

github/spec-kit · 14 tokens

speckit.bug.fix

Apply the remediation from a bug assessment and record what was changed.

github/spec-kit · 12 tokens