ashbrener/statusbar
skills/statusbar/SKILL.md
⛁ Manage your statusbar: the persistent gauge showing model, rate limits, context %, directory and git branch at the bottom of Claude Code
development
Updated Apr 23, 2026
$ install --global
skillsauthnpx skillsauth add ashbrener/claude-code-statusbar statusbarInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 24, 2026, 1:00 AM9.2s1 file scanned
SKILL.md
- name:
- statusbar
- description:
- ⛁ Manage your statusbar: the persistent gauge showing model, rate limits, context %, directory and git branch at the bottom of Claude Code
Statusbar
A single command to manage the Claude Code statusbar. Detect current state and act accordingly.
Step 1: Detect current state
Check if the statusbar is installed:
- Does
~/.claude/statusbar-command.shexist? - Does
~/.claude/settings.jsoncontain astatusLinekey? - Does
~/.claude/statusbar-config.jsonexist?
Step 2: Route based on state
If NOT installed
Tell the user the statusbar is not installed and show what it looks like:
Opus 4.6 5hr:██░░░░░░░░ 12% ctx:██░░░░░░░░ 24% Code/myproject main
Ask: Install now?
If yes, follow the install steps from /statusbar-install.
If already installed
Show current configuration and a live preview of what the statusbar looks like.
Then ask what they'd like to do:
- Configure — change segments, order, bar style, labels, display mode, thresholds
- Reset — delete config and restore defaults
- Uninstall — remove statusbar and restore previous config
Configure
Walk through options interactively. Only ask about what the user wants to change — don't force them through every option.
Available settings:
| Setting | Default | Options |
|---------|---------|---------|
| Segments | model, rate, context, directory, branch | Pick which to show and reorder |
| Display mode | used | used (24% consumed) or remaining (76% available) |
| Color ramp | same | same (brightens in gauge color) or red (shifts to yellow/red) |
| Bar style | ██░░ | ■■□□, ●●○○, ##--, or custom characters |
| Bar width | 10 | Any number |
| Labels | rate: auto, context: ctx | Custom strings (e.g. ctx → window) |
| Thresholds | 50% / 80% | When colors shift |
| Directory | relative to ~/ | Absolute, or strip custom prefix |
Save changes to ~/.claude/statusbar-config.json. Only include keys the user customized.
Reset
Delete ~/.claude/statusbar-config.json. The statusbar script falls back to built-in defaults.
Uninstall
Follow the steps from /statusbar-uninstall. Restore any backed-up configuration.
Important
- The statusbar script is installed at
~/.claude/statusbar-command.sh(Claude's expected filename) - The config is at
~/.claude/statusbar-config.json(our config) - The settings.json key is
statusLine(Claude's key name) - After any changes, remind the user to restart Claude Code
jqis required at runtime for the statusbar script
Related Skills
openclaw/openclaw-secret-scanning-maintainer
development
VerifiedTrustedCommunity
Maintainer-only workflow for handling GitHub Secret Scanning alerts on OpenClaw. Use when Codex needs to triage, redact, clean up, and resolve secret leakage found in issue comments, issue bodies, PR comments, or other GitHub content.
357,764SKILL.mdUpdated Apr 15, 2026
openclaw/openclaw-release-maintainer
development
VerifiedTrustedCommunity
Maintainer workflow for OpenClaw releases, prereleases, changelog release notes, and publish validation. Use when Codex needs to prepare or verify stable or beta release steps, align version naming, assemble release notes, check release auth requirements, or validate publish-time commands and artifacts.
357,764SKILL.mdUpdated Apr 10, 2026
openclaw/openclaw-qa-testing
development
VerifiedTrustedCommunity
Run, watch, debug, and extend OpenClaw QA testing with qa-lab and qa-channel. Use when Codex needs to execute the repo-backed QA suite, inspect live QA artifacts, debug failing scenarios, add new QA scenarios, or explain the OpenClaw QA workflow. Prefer the live OpenAI lane with regular openai/gpt-5.4 in fast mode; do not use gpt-5.4-pro or gpt-5.4-mini unless the user explicitly overrides that policy.
357,764SKILL.mdUpdated Apr 10, 2026
openclaw/openclaw-parallels-smoke
development
VerifiedTrustedCommunity
End-to-end Parallels smoke, upgrade, and rerun workflow for OpenClaw across macOS, Windows, and Linux guests. Use when Codex needs to run, rerun, debug, or interpret VM-based install, onboarding, gateway smoke tests, latest-release-to-main upgrade checks, fresh snapshot retests, or optional Discord roundtrip verification under Parallels.
357,764SKILL.mdUpdated Apr 10, 2026