How do I install the Statusline Setup skill?

Run npx skillmds@latest add master5d/statusline-setup in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Statusline Setup safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Statusline Setup?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Statusline Setup free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Statusline Setup?

master5d (@master5d) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Statusline Setup by master5d — Agent Skill

Name: Statusline Setup
Author: master5d

Statusline Setup

Set up, fix, or update the Claude Code footer status bar (statusline). Use this skill whenever the user mentions "status line", "statusline", "status bar", "footer bar", "fix my statusline", "set up status line", "context bar", or wants to see token/model info in the Claude Code footer. Covers initial setup, wiring settings.json, dependency checks (jq), and updating the statusline script.

master5d 163b317 2 files · 12.9 KB Updated Sep 17, 2026

File contents

Claude Code Statusline Setup

A custom statusline showing model info, context usage, session tokens, and weekly token tracking in the Claude Code footer.

Layout (5 lines)

Sonnet 4.6 (200k)  ●●●○○○○○○○○○○○○○○○○○  | ✏  12% | MyProject |
session  ●●○○○○○○○○  12%  7kin · 3kout  🕐20:51
weekly   ~18k est  🕐Tue 25 Mar
🎁 2× off-peak  → std in 2h 15m  ·  3d left   ← (promo lines, time-limited)
►► bypass permissions on (shift+tab to cycle)  ← (only when bypass active)

Setup Steps

1. Check dependency: `jq`

jq --version

If missing on Windows/Scoop:

scoop install jq

The settings.json command must explicitly add jq to PATH since Claude Code doesn't inherit the full shell PATH:

"PATH=\"/c/Users/sasha/scoop/apps/jq/1.8.1:$PATH\" bash \"$HOME/.claude/statusline-command.sh\""

Adjust the path to match where scoop installed jq (scoop which jq).

2. Write the script

Copy references/statusline-command.sh to ~/.claude/statusline-command.sh (make executable on Unix/WSL: chmod +x).

3. Wire settings.json

Edit ~/.claude/settings.json — add/update the statusLine block:

{
  "statusLine": {
    "type": "command",
    "command": "PATH=\"/c/Users/sasha/scoop/apps/jq/1.8.1:$PATH\" bash \"$HOME/.claude/statusline-command.sh\""
  }
}

If jq is on PATH already (Linux/macOS), simplify to:

{
  "statusLine": {
    "type": "command",
    "command": "bash \"$HOME/.claude/statusline-command.sh\""
  }
}

State file

Token tracking persists to ~/.claude/statusline-weekly.json. Safe to delete to reset weekly counter.

Common issues

Symptom	Cause	Fix
Status bar empty / blank	`jq` not found	Add jq to PATH in the command
All zeros / nulls	Old jq version	`scoop update jq`
Weekly count wrong	State file corrupt	Delete `~/.claude/statusline-weekly.json`
Math errors in output	Bash arithmetic overflow	Verify `$(( ))` used (not `bc`)
Promo section still showing	Date check hardcoded	Edit `PROMO_END_NUM` in script

Updating the script

When updating:

Read ~/.claude/statusline-command.sh first
Make targeted edits — don't overwrite the whole file unless replacing entirely
The script receives Claude Code's status JSON on stdin — all data comes from there
Test with: echo '{"model":{"display_name":"Claude Sonnet 4.6"},"context_window":{"context_window_size":200000,"used_percentage":15,"total_input_tokens":7000,"total_output_tokens":3000},"workspace":{"project_dir":"/test/project"}}' | bash ~/.claude/statusline-command.sh

Reference implementation

See references/statusline-command.sh for the full script. Read it before modifying.

---name: statusline-setupdescription: Set up, fix, or update the Claude Code footer status bar (statusline). Use this skill whenever the user mentions "status line", "statusline", "status bar", "footer bar", "fix my statusline", "set up status line", "context bar", or wants to see token/model info in the Claude Code footer. Covers initial setup, wiring settings.json, dependency checks (jq), and updating the statusline script.---# Claude Code Statusline SetupA custom statusline showing model info, context usage, session tokens, and weekly token tracking in the Claude Code footer.## Layout (5 lines)```Sonnet 4.6 (200k) ●●●○○○○○○○○○○○○○○○○○ | ✏ 12% | MyProject |session ●●○○○○○○○○ 12% 7kin · 3kout 🕐20:51weekly ~18k est 🕐Tue 25 Mar🎁 2× off-peak → std in 2h 15m · 3d left ← (promo lines, time-limited)►► bypass permissions on (shift+tab to cycle) ← (only when bypass active)```## Setup Steps### 1. Check dependency: `jq````bashjq --version```If missing on Windows/Scoop:```bashscoop install jq```The `settings.json` command must explicitly add jq to PATH since Claude Code doesn't inherit the full shell PATH:```json"PATH=\"/c/Users/sasha/scoop/apps/jq/1.8.1:$PATH\" bash \"$HOME/.claude/statusline-command.sh\""```Adjust the path to match where scoop installed jq (`scoop which jq`).### 2. Write the scriptCopy `references/statusline-command.sh` to `~/.claude/statusline-command.sh` (make executable on Unix/WSL: `chmod +x`).### 3. Wire settings.jsonEdit `~/.claude/settings.json` — add/update the `statusLine` block:```json{ "statusLine": { "type": "command", "command": "PATH=\"/c/Users/sasha/scoop/apps/jq/1.8.1:$PATH\" bash \"$HOME/.claude/statusline-command.sh\"" }}```If jq is on PATH already (Linux/macOS), simplify to:```json{ "statusLine": { "type": "command", "command": "bash \"$HOME/.claude/statusline-command.sh\"" }}```## State fileToken tracking persists to `~/.claude/statusline-weekly.json`. Safe to delete to reset weekly counter.## Common issues| Symptom | Cause | Fix ||---------|-------|-----|| Status bar empty / blank | `jq` not found | Add jq to PATH in the command || All zeros / nulls | Old jq version | `scoop update jq` || Weekly count wrong | State file corrupt | Delete `~/.claude/statusline-weekly.json` || Math errors in output | Bash arithmetic overflow | Verify `$(( ))` used (not `bc`) || Promo section still showing | Date check hardcoded | Edit `PROMO_END_NUM` in script |## Updating the scriptWhen updating:- Read `~/.claude/statusline-command.sh` first- Make targeted edits — don't overwrite the whole file unless replacing entirely- The script receives Claude Code's status JSON on stdin — all data comes from there- Test with: `echo '{"model":{"display_name":"Claude Sonnet 4.6"},"context_window":{"context_window_size":200000,"used_percentage":15,"total_input_tokens":7000,"total_output_tokens":3000},"workspace":{"project_dir":"/test/project"}}' | bash ~/.claude/statusline-command.sh`## Reference implementationSee `references/statusline-command.sh` for the full script. Read it before modifying.

Frequently asked questions