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.
/plugin marketplace add SienkLogic/plan-build-run/plugin install pbrWrote 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.
[](https://agentmods.dev/skills/sienklogic/plan-build-run/statusline)<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.
<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>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.
| Model | Per session | Once 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 |
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`). 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.
- The script lives at
${CLAUDE_PLUGIN_ROOT}/scripts/status-line.js - Resolve
${CLAUDE_PLUGIN_ROOT}to its absolute path usingpwdor by checking the plugin root - If running from a local plugin dir (
claude --plugin-dir .), the path is the local repo'splugins/pbr/scripts/status-line.js - If running from the installed plugin cache (
~/.claude/plugins/cache/), use that path - Verify the script exists with
lsbefore 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
statusLinekey 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
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.
- 1mo ago First seen · 152 lines · 15 tokens per session scan B 02ae2ab8540f
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.
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.
session-save
Save the current session state (decisions, modified files, current status, and next steps) to a handoff file for later resume.
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.
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.
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.
session
Session lifecycle management. Parent skill for session-related skills: learning (pattern extraction) and compact (context compression).