statusline

statusline is a skill for Claude Code from SienkLogic/plan-build-run. It costs 15 tokens per session (1,407 once invoked), scanned B, original, MIT.

A setup tool for installing or configuring a live project-status display in the Claude Code terminal.

In plain words
What is it for?
Use it to install, remove, or preview the Plan-Build-Run status line.
Why use it?
It keeps key project information visible while you work instead of requiring separate status checks.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: reads .claude/ paths; names the AskUserQuestion tool; 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 pbr plugin — 44 skills, 71 commands, 18 agents, 3 hooks shipped together

Good fit Use it to install, remove, or preview the Plan-Build-Run status line.

Compare 6 skills from other repositories ↓
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 SienkLogic/plan-build-run
Claude Code
/plugin install pbr

Made for: Claude Code.

Or install pbr, the plugin that ships this one along with the rest of its 44 skills, 71 commands, 18 agents, 3 hooks.

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/sienklogic/plan-build-run/statusline/github.svg)](https://agentmods.dev/skills/sienklogic/plan-build-run/statusline)
Your own site
<a href="https://agentmods.dev/skills/sienklogic/plan-build-run/statusline"><img src="https://agentmods.dev/badge/skills/sienklogic/plan-build-run/statusline/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

Your own site · 80×15
<a href="https://agentmods.dev/skills/sienklogic/plan-build-run/statusline"><img src="https://agentmods.dev/badge/skills/sienklogic/plan-build-run/statusline.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 15 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,407 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.00015 $0.01407
Opus 5.5 $0.00006 $0.00563
Sonnet 5.5 $0.00003 $0.00281
Haiku 4.5 $0.00002 $0.00141

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

Security

Grade B, and why

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 1mo 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.

Read `~/.claude/settings.json` (or `$HOME/.claude/settings.json`).
plugins/pbr/skills/statusline/SKILL.md · 152 lines

How it starts

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

STOP — DO NOT READ THIS FILE. You are already reading it. This prompt was injected into your context by Claude Code's plugin system. Using the Read tool on this SKILL.md file wastes ~3,000 tokens. Begin executing Step 0 immediately.

Step 0 — Immediate Output

Before ANY tool calls, display this banner:

╔══════════════════════════════════════════════════════════════╗
║  PLAN-BUILD-RUN ► STATUS LINE                                ║
╚══════════════════════════════════════════════════════════════╝

Then proceed to Step 1.

/pbr:statusline — Status Line Setup

The PBR status line displays live project state (phase, plan, status, git branch, context usage) in the Claude Code terminal status bar.


Subcommand Parsing

Parse $ARGUMENTS:

Argument Action
install or empty Install/enable the status line
uninstall or remove Remove the status line configuration
preview Show what the status line looks like without installing

Subcommand: install (default)

Step 1: Locate the status-line script

CRITICAL: You must resolve the correct absolute path to status-line.js. Do NOT hardcode paths.

  1. The script lives at ${CLAUDE_PLUGIN_ROOT}/scripts/status-line.js
  2. Resolve ${CLAUDE_PLUGIN_ROOT} to its absolute path using pwd or by checking the plugin root
  3. If running from a local plugin dir (claude --plugin-dir .), the path is the local repo's plugins/pbr/scripts/status-line.js
  4. If running from the installed plugin cache (~/.claude/plugins/cache/), use that path
  5. Verify the script exists with ls before proceeding. If it doesn't exist, show an error and stop.

Store the resolved absolute path as SCRIPT_PATH.

Step 2: Read current settings

Read ~/.claude/settings.json (or $HOME/.claude/settings.json).

  • If the file doesn't exist: start with an empty object {}
  • If it exists: parse the JSON content
  • Check if statusLine key already exists:
    • If yes and points to the same script: inform user "PBR status line is already installed." and stop (unless they want to reconfigure)
    • If yes but points to a different command: warn user and ask if they want to replace it

Read the full file on GitHub · 152 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. 1mo ago First seen · 152 lines · 15 tokens per session scan B 02ae2ab8540f

Subscribe to this mod's changes

statusline is a skill published in the GitHub repository SienkLogic/plan-build-run (19 stars, last pushed 6mo ago), licensed MIT. It adds 15 tokens to every session and 1,407 once invoked, about $0.0001 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-09-03.

Related

Other skills, from other repositories

rtk-optimizer

Wrap high-verbosity shell commands with RTK to reduce token consumption. Use when running git log, git diff, cargo test, pytest, or other verbose CLI output that wastes context window tokens.

FlorianBruniaux/claude-code-ultimate-guide · 44 tokens

session-save

Save the current session state (decisions, modified files, current status, and next steps) to a handoff file for later resume.

FlorianBruniaux/claude-code-ultimate-guide · 31 tokens

handoff-create

Generate a structured handoff document from the current session. Captures scope, relevant files with line numbers, key discoveries, work completed, current status, next steps, and code snippets. Use before ending a session or handing work to another agent.

FlorianBruniaux/claude-code-ultimate-guide · 53 tokens

handoff-update

Update an existing handoff document with current session progress. Applies section-specific merge rules: append-only for Work Done (never deletes history), replace for Status and Next Steps, merge for Files and Discoveries. Falls back to creating a new handoff if no source file is found.

FlorianBruniaux/claude-code-ultimate-guide · 60 tokens

handoff-resume

Load a handoff document and resume work from where a previous session left off. Parses scope, file references, completed work, and next steps, then confirms understanding before proceeding.

FlorianBruniaux/claude-code-ultimate-guide · 40 tokens

session

Session lifecycle management. Parent skill for session-related skills: learning (pattern extraction) and compact (context compression).

xiaobei930/cc-best · 24 tokens