Skill · Open source

claude-code-statusline

A four-line Claude Code status line: context-window usage, the 5h and 7d limit windows with pace markers, git state, and cache stats. It runs on pure Node with no dependencies.

Role INSTRUMENTATION Language JavaScript Pushed 05 Aug 2026

View on GitHub → Full README on GitHub →

Open sourceThe short version

What it does

A four-line Claude Code status line: context-window usage, the 5h and 7d limit windows with pace markers, git state, and cache stats. It runs on pure Node with no dependencies.

Install

curl -fsSL https://raw.githubusercontent.com/lucasyhzhu-debug/claude-code-statusline/main/statusline-vbw.cjs -o ~/.claude/statusline-vbw.cjs

Pairs with

fresh

Source

github.com/lucasyhzhu-debug/claude-code-statusline

Why use it

It answers the two questions you keep asking mid-session: how full is the context window, and how close am I to the limit.

More of the toolchain

SCHEDULING JavaScript

fresh

Fires a prompt the moment your next 5-hour usage window resets, either in the same session or in a clean headless run with --clear. Windows-first.

Why use itThe heavy runs start on a full quota instead of dying at 80% through.

pushed 19 Jun read

VISIBILITY Markdown

ai-seo

Works on getting cited by ChatGPT, Perplexity, Claude and Google AI Overviews rather than ranked. Covers the visibility audit, extractable structure, machine-readable files like llms.txt and /pricing.md, and what agents need to read a page at all.

Why use itTwo gates bound every run. It will not start without a resolving target and a query to measure against, and it will not end without writing the findings to a file first — audit runs have a habit of dissolving into a closed session with nothing saved.

pushed 11 Aug read

AUDIT Markdown

seo-audit

A technical and on-page SEO audit skill that refuses to audit a target that is not there. It opens with a preflight gate: before reading its own next section, it checks for site files in the working directory or a live URL that resolves, and aborts naming what is missing.

Why use itPoint audit tooling at an empty directory and it will hand you a confident report about nothing. This one stops instead, and ships a table of the excuses an agent uses to talk itself past the gate.

pushed 11 Aug read