Skill Detail

Monitor Claude Code sessions with ccstatusline

Configure Claude Code's status line with live model, token, cost, git, sandbox, cache, CI, and session health signals so operators can supervise coding-agent work from the terminal.

Developer ToolsClaude Code
Developer Tools Claude Code Security Reviewed
⭐ 13.2k GitHub stars ⬇ 150.4k/wk npm
COPY SKILL INSTRUCTIONS (OPTIONAL)
npx skills add agentskillexchange/skills --skill monitor-claude-code-sessions-with-ccstatusline Copy
Uses the third-party skills CLI, not an ASE-owned installer. Check your agent’s compatibility. This copies instructions; complete the upstream tool setup below separately.
At a glance
Tools required
Claude Code CLI, Node.js, npm or Bun
Install & setup
Install with npm install -g ccstatusline or the documented Bun path, then run the ccstatusline setup/configuration flow and enable it as Claude Code's statusLine command. Use the TUI to choose widgets for model, usage, cost, git, CI, cache, sandbox, and health signals.
Author
sirmalloc
Publisher
Individual
Last updated
Oct 10, 2026
Quick brief

Use ccstatusline when a Claude Code operator needs a durable terminal status line for active agent sessions. It exposes configurable widgets for model identity, context usage, token speed, cost, git state, pull requests, CI status, sandbox mode, cache state, compaction, and Claude service health so long-running coding sessions can be monitored without repeatedly opening separate commands or dashboards.

How it works

What this skill actually does

This is skill-shaped because the repeatable job is operational supervision of Claude Code sessions through the documented statusLine hook and ccstatusline configuration flow. It is not a generic terminal theming package, analytics platform, or broad JavaScript library listing. Invoke it when the operator wants visible session telemetry and guardrail cues inside Claude Code, not when they only need decorative prompt styling.

Inputs and prerequisites: Claude Code CLI, Node.js, npm or Bun.

Setup notes: Install with npm install -g ccstatusline or the documented Bun path, then run the ccstatusline setup/configuration flow and enable it as Claude Code’s statusLine command. Use the TUI to choose widgets for model, usage, cost, git, CI, cache, sandbox, and health signals.

Source and verification boundary: use https://github.com/sirmalloc/ccstatusline as the canonical reference before running the workflow; keep commands, API calls, CLI usage, and generated outputs reviewable against that upstream source.

Framework fit: publish this as a Claude Code workflow only when the operator can invoke the documented toolchain directly, rather than treating the upstream project as a generic product listing.