Statusline Setup
ListedConfigures your terminal status line with dynamic information like time, battery, and system load using b-open-io's AI.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add b-open-io/prompts --skill statusline-setup --full-depth -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
b-open-io
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.
No obfuscated payloads: failed
Contains 1 obfuscated or encoded payload pattern.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
What it found
- modules/plugin-kit/skills/statusline-setup/.clawnet/unsigned-skill.json:413776-character base64 literal
"opReturnHex": "6a2231394878696756345179427633744870515663554551797131707a5a56646f4175744d53182d2d2d0a6e616d653a207374617475736c696e652d73657475700a64657363726…
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned b-open-io/prompts at 3e198cc712.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 3e198cc712
- Scanned
- 11 files, 1,805 lines
About this skill
What it does
This skill allows you to configure a dynamic status line within your Claude Code environment, displaying contextual information at the bottom of the interface. The status line updates automatically as conversation messages change (up to every 300ms). You can customize what's displayed, including model name, Git branch, token usage, project colors, and session cost, using either a custom script or a widget-based approach.
When to use it
- You want to quickly see the Claude Code model you are using directly in your terminal.
- You need to monitor token usage for cost tracking purposes.
- You'd like to display Git branch information within your coding environment.
- You prefer a visual indicator of project colors or session costs.
Key capabilities
- Customizable Status Line: Displays dynamic information in the Claude Code interface.
- Multiple Approaches: Supports both manual script creation (for full control) and integration with the
ccstatuslinewidget. - Information Display: Shows model name, Git branch, project colors, token usage, session cost, current directory, and more.
- JSON Input: Receives structured JSON data containing information about the Claude Code environment.
Example prompts
While this skill is configured through settings rather than direct prompting, here are examples of what an agent might do after it has been installed:
- "Configure my status line to show the model name and Git branch."
- "Set up a status line using the
ccstatuslinewidget." - "Create a custom script for my status line that displays token usage."
Tips & gotchas
- Existing Configuration: The skill checks for existing status line configurations. Back up your current settings before proceeding.
- Manual Scripting: If using the manual scripting approach, you'll need to create and maintain a shell script (
~/.claude/statusline.sh) that processes JSON input. ccstatuslineDependency: Using theccstatuslinemethod requires installing this third-party tool separately.