npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

claude-context-meter

v1.0.5

Published

Persistent context window usage meter for the Claude Code status line

Readme

claude-context-meter

A Claude Code plugin that adds a persistent context window usage meter to the status line. After every API response you'll see something like:

Context: 24k (18%) · [GitHub/my-project/main]

Color-coded by pressure level:

| Zone | Token range | Context numbers | VCS segment | |--------|------------------|-----------------|---------------------| | Green | < 70,000 | Green | Gray (clean) / Cyan (dirty) | | Yellow | 70,000–100,000 | Yellow | Gray (clean) / Cyan (dirty) | | Red | > 100,000 | Red | Gray (clean) / Cyan (dirty) |

In the red zone a suggestion is appended:

Context: 112k (56%) · Consider /compact or /clear · [GitHub/my-project/main]

VCS segment — if you're inside a git repository, the current platform, repo, and branch are shown at the end of the line. The segment turns cyan with a * when there are uncommitted changes:

Context: 24k (18%) · [GitHub/my-project/main*]

The status line updates automatically — no polling or background process required.

Installation

npx claude-context-meter install

This copies the plugin to ~/.claude/plugins/context-meter/ and updates ~/.claude/settings.json automatically. Open a new Claude Code session to activate it.

Uninstallation

npx claude-context-meter uninstall

This removes the plugin files and cleans up the statusLine entry from ~/.claude/settings.json. Open a new Claude Code session to complete the removal.

Prerequisites

  • Claude Code (any version that supports the statusLine setting)
  • Node.js ≥ 18 — already installed as part of Claude Code; no additional installation required

Verifying the installation

After opening a new Claude Code session you should see a status line that reads:

Context: 0 (0%) · [GitHub/my-project/main]

Send any message to Claude. After the API response the token count and percentage will update. If the status line does not appear, check that:

  • You opened a new Claude Code session after running the installer
  • ~/.claude/settings.json contains a statusLine entry pointing to the plugin

Running tests

node --test tests/test_context_meter.js