Skip to content
Back to search

ilia-pluzhnikov

MarketplaceWorks with Claude CodeGitHub

Claude Code plugins by Ilia Pluzhnikov

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/ilia-pluzhnikov/claude-code-statusline with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/ilia-pluzhnikov/claude-code-statusline'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/ilia-pluzhnikov--claude-code-statusline/badge.svg)](/listings/ilia-pluzhnikov--claude-code-statusline)

HTML

<a href="/listings/ilia-pluzhnikov--claude-code-statusline"><img src="/api/listings/ilia-pluzhnikov--claude-code-statusline/badge.svg" alt="findsafeskills safety rating" /></a>

Install

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

As a Claude Code plugin

/plugin marketplace add ilia-pluzhnikov/claude-code-statusline
/plugin install statusline-for-claude-code@ilia-pluzhnikov
/statusline-for-claude-code:setup

Claude Code doesn't let a plugin switch the status line on by itself (from a plugin's settings it applies only `agent` and `subagentStatusLine`), so the plugin needs one setup step. `/statusline-for-claude-code:setup` shows your current `statusLine` and the one it proposes, and only after you confirm writes that single key to `~/.claude/settings.json`, keeping a backup in `settings.json.bak`. From then on plugin updates reach the status line without running setup again: a `SessionStart` hook keeps a copy of `statusline.js` in the plugin's data folder current, and the setting points at that copy.

To remove it, restore `settings.json.bak` (or delete the `statusLine` key), then uninstall the plugin.

What the plugin runs, reads and writes

- **`SessionStart` hook** (`scripts/stage-statusline.js`): copies the plugin's `statusline.js` into its data folder, `~/.claude/plugins/data/<plugin-id>/`, when the copy is missing or differs. Nothing else. - **`/statusline-for-claude-code:setup`** (`scripts/configure-statusline.js`): reads `~/.claude/settings.json` and, after your confirmation, rewrites its `statusLine` key and saves the previous file as `settings.json.bak`. - **The status line itself** (`statusline.js`): reads the JSON Claude Code passes on stdin; runs local, read-only `git` commands (`status`, `branch`, `rev-parse`, `rev-list`) in the working directory with a 1 s timeout; on Claude Code builds older than 2.1.251 reads the last 16 KB of the session transcript for the prompt-cache timer; writes `claude-ctx-<session_id>.json` to the system temp folder. - **No network.** Nothing is fetched or sent anywhere, and no personal data is stored. The optional companion hook below is not part of the plugin.

Manually

1. **Clone or download** this repo. 2. **Drop `statusline.js`** anywhere you like. The natural location is `~/.claude/hooks/statusline.js`. 3. **Wire it up** in `~/.claude/settings.json`:

   {
     "statusLine": {
       "type": "command",
       "command": "node \"/absolute/path/to/statusline.js\"",
       "refreshInterval": 60
     }
   }

On Windows use forward slashes inside the JSON string: `"node \"C:/Users/you/.claude/hooks/statusline.js\""`.

`refreshInterval: 60` re-runs the script every 60 seconds in addition to event-driven updates (new assistant message, `/compact`, permission mode change, vim mode toggle). Without it, the cache TTL countdown freezes in idle — Claude Code only refreshes the statusline on those events, so a value rendered 50 minutes ago will keep showing `60m remaining` until you press Enter. 60 seconds is enough to step through the color thresholds (dim → yellow → red) cleanly while staying cheap (on Claude Code ≥2.1.251 the TTL comes straight from stdin; older builds read only the last 16 KB of the session transcript). Requires Claude Code ≥2.1.97.

4. **Restart Claude Code.** That's it.

The script reads the standard Claude Code statusline JSON from stdin (model, workspace, session, context window, rate limits) and writes a single ANSI-coloured line to stdout. It exits silently on any error so a broken statusline never blocks your session.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 15 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. {
  2. "name": "ilia-pluzhnikov",
  3. "owner": {
  4. "name": "Ilia Pluzhnikov",
  5. "url": "https://github.com/ilia-pluzhnikov"
  6. },
  7. "description": "Claude Code plugins by Ilia Pluzhnikov",
  8. "plugins": [
  9. {
  10. "name": "statusline-for-claude-code",
  11. "source": "./",
  12. "description": "A dependency-free Node.js status line for Claude Code: model and effort, live git state, context window, prompt-cache state and rate limits on one color-coded line."
  13. }
  14. ]
  15. }
README.md · README · 197 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. # Claude Code Statusline
  2. <img width="1899" height="134" alt="image" src="https://github.com/user-attachments/assets/0f10afac-e1be-44f5-a953-d37132903765" />
  3. A feature-rich, single-file Node.js statusline for [Claude Code](https://claude.ai/code).
  4. One line at the bottom of your terminal that tells you everything you actually need:
  5. which model you're on, the live git state of your repo, how much context you've
  6. burned, your prompt-cache hit/write state, and your subscription rate limits.
  7. No dependencies. No build step. Works on macOS, Linux, and Windows.
  8. ## Preview
  9. ```
  10. Op4.7:hg (1m) │ tweaks ▸ claude-…tusline (main) │ 3M 1? ↑2 push │ ██░░░ 480k/1M │ cache 87% ↓75k +360 1h:42m │ 5h:35%(2h15m) │ 7d:42%(4d)
  11. ```
  12. Each segment is color-coded (dim, bright, cyan, pink, green, yellow, orange, red) so the
  13. shape of the line itself communicates urgency at a glance. Labels are aggressively
  14. shortened so the line fits your terminal: the width budget is read from the `COLUMNS`
  15. environment variable that Claude Code exports to the script (v2.1.153+), with a fixed
  16. 100-column fallback for older builds and manual runs.
  17. <img width="1280" height="636" alt="image" src="https://github.com/user-attachments/assets/c07f4e46-61cb-473e-99d6-d7b06a3fa3ec" />
  18. ## What you see, left to right
  19. | Segment | Meaning |
  20. |---------|---------|
  21. | `Op4.7 (1m)` | Current model, abbreviated: family (`Op`/`So`/`Ha`/`My`/`Fb`) glued to the version + context size (dim). `Opus 4.7 (1M context)` becomes `Op4.7 (1m)`, `Fable 5` becomes `Fb5`. Unrecognised model names are shown as-is. |
  22. | `Op4.7:hg` | Reasoning-effort tier as a lowercase code colon-glued to the model (same dim shade): `lo`/`md`/`hg`/`xhg`/`max` for `low`/`medium`/`high`/`xhigh`/`max`. The one exception is `max`, rendered in red: max is the most expensive tier, rarely a default, and easy to leave switched on after a one-off `/effort max`. Reflects the live value (including mid-session `/effort` changes); the context size trails it — `Op4.7:hg (1m)`. Shown only on models that report `effort.level`; absent on models that don't support reasoning effort |
  23. | `stl:expl` | Active output style, shown only when it isn't `default`: `expl`/`learn`/`conc`/`proact` for the built-in `Explanatory`/`Learning`/`Concise`/`Proactive`, custom styles lowercased and cut to 7 chars. A non-default style changes how Claude responds and is saved per project by `/config`, so it quietly differs between projects and is easy to forget. Dim label; the code takes the same pink as a low context bar |
  24. | `claude-…tusline (main)` | Working directory basename (dim) + current branch in cyan; shows `(HEAD@<sha>)` in red for detached HEAD. The basename is trimmed to a 15-char `head…tail` middle ellipsis (7 chars each side) **only when the full status line would otherwise exceed the width budget** (the terminal width from `COLUMNS`, 100 columns when it's absent) — short lines keep the full name |
  25. | `tweaks ▸ statusline (main)` | When the working directory has moved away from where the session was launched (`workspace.project_dir` ≠ `workspace.current_dir`, e.g. after a `cd`), the launch dir basename is prepended as a dim `▸` breadcrumb so it's clear the session — and its transcript — is rooted elsewhere than the current directory. Hidden when the two match. Short lines keep both names in full; once the line would cross the width budget, width is reclaimed in stages — the current-dir name is ellipsised, then the launch name, then the breadcrumb is dropped entirely |
  26. | `3M 1A 1D 1R 2? 1!` | Working tree status, bucketed by VS Code-style codes: `M` = modified, `A` = added/staged, `D` = deleted, `R` = renamed, `?` = untracked. All shown dim. `!` = unmerged conflict, rendered separately in **red** because it's the only one that blocks a commit. Empty buckets are hidden — clean repo shows nothing |
  27. | `↑2 push` / `↓1 pull` | Local branch is ahead/behind `origin/<branch>` |
  28. | `██░░░ 480k/1M` | Context window usage — 5-cell bar with half-block precision (`█▌░`, ~10% per step in 5 cells). When Claude Code provides absolute context counters, the bar is driven by `total_input_tokens / context_window_size` and the segment appends the raw counts (for example `480k/1M`). When only `remaining_percentage` is available, the bar falls back to `100 - remaining` |
  29. | `cache 87% ↓75k +360 1h:42m` | Prompt cache state. Read/write/input counters come from stdin `context_window.current_usage`. The TTL bucket (`1h`/`5m`) and countdown come from stdin `prompt_cache.ttl` / `expires_at` on Claude Code ≥2.1.251; older builds fall back to the session transcript for the last cache write's bucket and timestamp. Hit ratio is `read / (input + write + read)`: `≥90%` bold green, `≥75%` green, `≥50%` yellow, below that orange, and `0%` bold red for a full miss/invalidation. `↓` means tokens read from cache, `+` or `↑` means tokens written. After `/compact`, `cache:reset` appears while stdin `current_usage` is null but the session has already seen cache activity (`prompt_cache.caching_observed` on ≥2.1.251, the transcript on older builds) |
  30. | `5h:35%(2h15m)` | 5-hour rate limit usage + reset countdown (`Xh Ym` / `Mm`) |
  31. | `7d:42%(4d)` | 7-day rate limit usage + reset countdown. Coarse format: `Nd` while ≥ 2 days remain; `1dXh` for the final day (renders as `24h` at exactly 1 day so the unit doesn't lie); `Xh Ym` / `Mm` below 1 day |
  32. The context bar and rate-limit percentages share the same color scale:
  33. | Used | Color |
  34. |------|-------|
  35. | < 50% | pink |
  36. | 50-65% | yellow |
  37. | 65-80% | orange |
  38. | ≥ 80% | red with a 💀 prefix on the context bar |
  39. The context bar has one extra absolute-token rule: once `total_input_tokens`
  40. crosses **250k**, pink is promoted to yellow regardless of the percentage
  41. scale. 250k is the practical "already a lot" cliff — model output quality
  42. degrades and Anthropic's long-context pricing tier kicks in around there —
  43. so a 1M-context session at 250k/1M (25% used) shouldn't render as cozy pink.
  44. ## Installation
  45. ### As a Claude Code plugin
  46. ```
  47. /plugin marketplace add ilia-pluzhnikov/claude-code-statusline
  48. /plugin install statusline-for-claude-code@ilia-pluzhnikov
  49. /statusline-for-claude-code:setup
  50. ```
  51. **Installed from the Claude plugin directory?** The directory listing stays at
  52. v1.3.1: since November 2026 it accepts plugins with hooks or scripts only from
  53. organizations Anthropic has verified, so newer versions can't be published
  54. there. To get the current version, uninstall the directory copy, install from
  55. this repository with the commands above, and run
  56. `/statusline-for-claude-code:setup` again.
  57. Claude Code doesn't let a plugin switch the status line on by itself (from a
  58. plugin's settings it applies only `agent` and `subagentStatusLine`), so the
  59. plugin needs one setup step. `/statusline-for-claude-code:setup` shows your current
  60. `statusLine` and the one it proposes, and only after you confirm writes that
  61. single key to `~/.claude/settings.json`, keeping a backup in
  62. `settings.json.bak`. From then on plugin updates reach the status line without
  63. running setup again: a `SessionStart` hook keeps a copy of `statusline.js` in
  64. the plugin's data folder current, and the setting points at that copy. Until
  65. setup is done, that hook reminds you about it once, at the start of a session.
  66. To remove it, restore `settings.json.bak` (or delete the `statusLine` key),
  67. then uninstall the plugin.
  68. #### What the plugin runs, reads and writes
  69. - **`SessionStart` hook** (`scripts/stage-statusline.js`): copies the plugin's
  70. `statusline.js` into its data folder, `~/.claude/plugins/data/<plugin-id>/`,
  71. when the copy is missing or differs. If the `statusLine` key in
  72. `~/.claude/settings.json` doesn't run that copy yet, it shows a one-time
  73. reminder to run setup and leaves a `setup-hint-shown` marker file in the same
  74. folder. It writes nothing outside that folder.
  75. - **`/statusline-for-claude-code:setup`** (`scripts/configure-statusline.js`): reads
  76. `~/.claude/settings.json` and, after your confirmation, rewrites its
  77. `statusLine` key and saves the previous file as `settings.json.bak`.
  78. - **The status line itself** (`statusline.js`): reads the JSON Claude Code passes
  79. on stdin; runs local, read-only `git` commands (`status`, `branch`,
  80. `rev-parse`, `rev-list`) in the working directory with a 1 s timeout; on
  81. Claude Code builds older than 2.1.251 reads the last 16 KB of the session
  82. transcript for the prompt-cache timer; writes `claude-ctx-<session_id>.json`
  83. to the system temp folder.
  84. - **No network.** Nothing is fetched or sent anywhere, and no personal data is
  85. stored. The optional companion hook below is not part of the plugin.
  86. ### Manually
  87. 1. **Clone or download** this repo.
  88. 2. **Drop `statusline.js`** anywhere you like. The natural location is `~/.claude/hooks/statusline.js`.
  89. 3. **Wire it up** in `~/.claude/settings.json`:
  90. ```json
  91. {
  92. "statusLine": {
  93. "type": "command",
  94. "command": "node \"/absolute/path/to/statusline.js\"",
  95. "refreshInterval": 60
  96. }
  97. }
  98. ```
  99. On Windows use forward slashes inside the JSON string: `"node \"C:/Users/you/.claude/hooks/statusline.js\""`.
  100. `refreshInterval: 60` re-runs the script every 60 seconds in addition to event-driven updates (new assistant message, `/compact`, permission mode change, vim mode toggle). Without it, the cache TTL countdown freezes in idle — Claude Code only refreshes the statusline on those events, so a value rendered 50 minutes ago will keep showing `60m remaining` until you press Enter. 60 seconds is enough to step through the color thresholds (dim → yellow → red) cleanly while staying cheap (on Claude Code ≥2.1.251 the TTL comes straight from stdin; older builds read only the last 16 KB of the session transcript). Requires Claude Code ≥2.1.97.
  101. 4. **Restart Claude Code.** That's it.
  102. The script reads the standard Claude Code statusline JSON from stdin (model,
  103. workspace, session, context window, rate limits) and writes a single ANSI-coloured
  104. line to stdout. It exits silently on any error so a broken statusline never blocks your
  105. session.
  106. ## Optional companion hook
  107. [`optional-hooks/github-sync-check.js`](./optional-hooks/) is a `SessionStart`
  108. hook that warns about uncommitted files and tells you when your branch has drifted
  109. from `origin/<branch>`. It runs `git fetch` in the background so the next session
  110. has fresh data. It isn't part of the plugin and isn't required for the statusline
  111. itself; see [`optional-hooks/README.md`](./optional-hooks/README.md) to install it
  112. by hand.
  113. The `md-sync-check.js` and `sync-md.js` hooks and the `⚠ md drift` segment, which
  114. kept `CLAUDE.md` / `AGENTS.md` / `GEMINI.md` in sync, were removed in v1.3.0:
  115. Codex and Claude Code (v2.1.277+) read `AGENTS.md` directly, and Gemini CLI does
  116. once its `context.fileName` setting lists it, so a single `AGENTS.md` serves all
  117. three.
  118. ## How it stays fast
  119. - **All git checks are local.** No `git fetch`, no network, hard 1s timeout per command.
  120. - **Bridge file in `os.tmpdir()`.** The context-usage value is written to `claude-ctx-{session_id}.json` so other hooks (e.g. a `PostToolUse` context monitor) can read the same number without re-parsing stdin.
  121. - **Stdin timeout (3s)** — if Claude Code never sends data, the script exits cleanly instead of hanging.
  122. ## Cross-platform notes
  123. - **Windows:** the script uses `windowsHide: true` on every git subprocess call, so no
  124. console flashes appear during git polling.
  125. - **Path separators:** filesystem paths use `path.join` and `os.homedir()`;
  126. Claude transcript lookup intentionally mirrors Claude Code's project-slug
  127. convention by replacing drive colons, path separators, and dots with `-`.
  128. ## Customization
  129. The script is 370 lines of dependency-free Node.js. Open it and tweak.
  130. The most common customizations:
  131. - **Hide the cache segment** — delete the `Prompt cache state` block. Useful if you don't run Claude Code in this terminal or don't want token counts visible.
  132. - **Change the colour thresholds** — search for `< 50` / `< 65` / `< 80` and edit.
  133. - **Hide the model name** — remove `\`\x1b[2m${model}\x1b[0m\`` from the `segments` array at the bottom.
  134. - **Use a different separator** — change `' │ '` (the `│` character) on the final line.
  135. ## Requirements
  136. - Node.js (any modern version — uses only built-in modules)
  137. - Claude Code with statusline support (`statusLine` in `settings.json`)
  138. - Optional: `git` on `PATH` for the git-status segment
  139. ## А еще я пишу статьи
  140. А если хотите получше освоить Claude Code и вообще принцип работы AI, то у меня есть различные статьи на эту тему
  141. [https://ilia-pro-ai.com/](https://ilia-pro-ai.com/articles/)
  142. <img width="1480" height="1123" alt="image" src="https://github.com/user-attachments/assets/cb8e6b16-2d60-4107-85c0-b01115cdb10e" />
  143. ## License
  144. MIT — see [LICENSE](./LICENSE).
  145. ## Credits
  146. Built by [Ilia Pluzhnikov](https://github.com/ilia-pluzhnikov).
  147. PRs and forks welcome.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.