Install the spend statusline

Plugins cannot set statusLine themselves, and the plugin's own directory moves on every version update, so this skill copies the files somewhere stable and points settings at that copy. Idempotent: safe to re-run after a plugin update.

Steps

1. Locate the source. The files ship with this plugin at ${CLAUDE_PLUGIN_ROOT}/statusline/:

   • spend-statusline.sh
   • config/calendar.conf (the work-week and holiday calendar)
   • config/display.conf (which elements the statusline shows)

   Resolve the config dir as ${CLAUDE_CONFIG_DIR:-$HOME/.claude}; call it $CFG below.

2. Copy to the stable location, preserving the subfolders:

   CFG="${CLAUDE_CONFIG_DIR:-$HOME/.claude}"
   mkdir -p "$CFG/statusline/config"
   cp "${CLAUDE_PLUGIN_ROOT}/statusline/spend-statusline.sh" "$CFG/statusline/"
   [ -e "$CFG/statusline/config/calendar.conf" ] || \
     cp "${CLAUDE_PLUGIN_ROOT}/statusline/config/calendar.conf" "$CFG/statusline/config/"
   [ -e "$CFG/statusline/config/display.conf" ] || \
     cp "${CLAUDE_PLUGIN_ROOT}/statusline/config/display.conf" "$CFG/statusline/config/"
   chmod +x "$CFG/statusline/spend-statusline.sh"

   The script is refreshed every time. calendar.conf and display.conf are copied only if absent — once installed they are the user's own (they may have edited them) and must not be overwritten on update.
3. Check the bash. The script needs bash 4.4+. On Linux and in Git Bash on Windows, bash is fine. On macOS the system bash is 3.2; the script hands itself to Homebrew's bash when one is installed, so check /opt/homebrew/bin/bash (Apple silicon) then /usr/local/bin/bash (Intel) with "$candidate" -c 'echo ${BASH_VERSINFO[0]}.${BASH_VERSINFO[1]}'. If neither reports 4.4 or newer, stop and tell the user to run brew install bash, then re-run this skill. The command below says plain bash either way; never write an absolute bash path into it.
4. Wire settings. Read $CFG/settings.json. Show the user the exact change before making it, then set statusLine.command to this text exactly as written, with the shell expressions left unexpanded:

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

   Claude Code runs the command through a shell, so each machine resolves the path for itself: the same settings file then works when ~/.claude is shared with a devcontainer or another user account whose home directory differs. Write it with a JSON tool (jq --arg) or check the result with jq -r .statusLine.command, which must print bash "${CLAUDE_CONFIG_DIR:-$HOME/.claude}/statusline/spend-statusline.sh".
   • Updating an earlier install whose command names the script by an absolute path (bash /home/<user>/.claude/statusline/spend-statusline.sh, or a Homebrew bash path in front): that is this plugin's own command, so replace it with the form above without asking, keeping any inline knobs (NAME=value words) in front of bash.
   • A different statusline already set (a command naming another script): say so and ask before replacing it.
   • Shared config dir. If the user says this config dir is shared with a devcontainer, another machine or another account, suggest pinning the spend clock with an inline CLAUDE_SPEND_TZ=<their zone> in front of bash (for example CLAUDE_SPEND_TZ=America/Chicago bash "${CLAUDE_CONFIG_DIR:-$HOME/.claude}/..."). The cache lives in the shared dir, and two machines on different time zones (containers often run on UTC) disagree about the date for part of each day, which would reset the day bar and refetch on every render.
   • Never touch any other key.
5. Run the doctor on the installed copy, with any inline knobs the statusLine command has in front, and show its output:

   bash "$CFG/statusline/spend-statusline.sh" --doctor

   It checks the tools (jq, curl, awk; a missing one comes with the install command for this platform), the credentials, fetches the usage figures once in the foreground, and ends with bars: will show or bars: hidden after the step that failed. If the bars will be hidden, explain the failing line (an API-key session has no usage token; a plan with no dollar figure cannot show spend bars; a missing limit needs CLAUDE_SPEND_MONTHLY_LIMIT) and point at /spend-statusline:doctor for later.
6. Tell the user the new statusline appears on the next refresh, no restart needed (Claude Code picks up the settings change live). A successful doctor run has already filled the cache, so the bars show on the first render. Point them at the plugin's README.md for what the bars mean and the knobs (CLAUDE_SPEND_MONTHLY_LIMIT, CLAUDE_SPEND_TZ, CLAUDE_SPEND_REFRESH, CLAUDE_SPEND_CALENDAR, CLAUDE_SPEND_DISPLAY), at /spend-statusline:calendar for editing the calendar (work week, holidays, PTO), at /spend-statusline:display for hiding or showing elements (the pace tick, the cache cue, the repository row), and at /spend-statusline:doctor if the bars ever go blank.

Do not

• Do not point statusLine at the plugin directory — it changes on update.
• Do not overwrite an existing calendar.conf or display.conf.
• Do not edit settings without showing the change first.
• Do not expand ${CLAUDE_CONFIG_DIR:-$HOME/.claude} or write an absolute path (to the script or to bash) into the command; the literal form is what lets a shared settings file work everywhere.
• Do not finish on macOS without a 4.4+ Homebrew bash; stop and name brew install bash.