setup-statusline

Configure a terminal status line in Claude settings for API usage and cost.

1|1|Updated Feb 1, 2026
One-click install
npx skills add https://github.com/zb-ss/claude-plugin-workflow --skill setup-statusline-zb-ss
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-statusline
Source: https://github.com/zb-ss/claude-plugin-workflow/tree/main/skills/setup-statusline
Command: npx skills add https://github.com/zb-ss/claude-plugin-workflow --skill setup-statusline-zb-ss

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of not knowing your Claude Code usage limits, context window utilization, and session cost while running the workflow, so you can avoid unexpected throttling and overspending.

Core Features & Use Cases

  • API-backed status display: Shows 5h rolling usage, 7d weekly usage, context window usage, and USD cost in the terminal status line.
  • Enable/disable configuration via settings: Adds or removes a statusLine command in ~/.claude/settings.json without overwriting other settings.
  • Graceful degradation: If OAuth credentials are missing, it still reports context/cost rather than failing entirely.
  • Operational prerequisites & troubleshooting: Verifies script location, JSON validity, and instructs users to restart Claude Code for changes to apply.

Quick Start

Run /workflow:setup-statusline enable to add the workflow status line configuration to your Claude settings.

Frequently Asked Questions about setup-statusline

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I show live Claude Code API usage limits and session cost in my terminal?

To show Claude Code usage and session cost, you can enable a real-time terminal status line that reports API usage limits, context window utilization, and USD cost by adding a statusLine command to your Claude settings file.

What usage metrics does the terminal status line display for Claude Code?

The terminal status line displays 5-hour rolling API usage, 7-day weekly usage, context window utilization, and real-time USD session cost to help you avoid unexpected throttling and overspending.

How do I configure Claude Code settings to add a status line without overwriting existing configurations?

Configuring the status line safely updates the ~/.claude/settings.json file by adding or removing the statusLine command with a resolved absolute node script path, preserving your other existing settings without overwriting them.

Does the Claude Code status line work without OAuth credentials?

Yes, the status line supports graceful degradation; if OAuth credentials are missing, it skips the usage-bar display but still reports context window utilization and session cost rather than failing entirely.

Why is my Claude Code status line not working after updating settings.json?

If your status line is not working, verify the script location path and JSON validity, then restart Claude Code completely because status line configuration changes require a session restart to apply.