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

@sriram-rach/clavis

v1.4.0

Published

Powerful enhancements for Claude Code — unlock the full potential of your AI coding assistant

Readme

      ___           ___           ___           ___                       ___
     /\  \         /\__\         /\  \         /\__\          ___        /\  \
    /::\  \       /:/  /        /::\  \       /:/  /         /\  \      /::\  \
   /:/\:\  \     /:/  /        /:/\:\  \     /:/  /          \:\  \    /:/\ \  \
  /:/  \:\  \   /:/  /        /::\~\:\  \   /:/__/  ___      /::\__\  _\:\~\ \  \
 /:/__/ \:\__\ /:/__/        /:/\:\ \:\__\  |:|  | /\__\  __/:/\/__/ /\ \:\ \ \__\
 \:\  \  \/__/ \:\  \        \/__\:\/:/  /  |:|  |/:/  / /\/:/  /    \:\ \:\ \/__/
  \:\  \        \:\  \            \::/  /   |:|__/:/  /  \::/__/      \:\ \:\__\
   \:\  \        \:\  \           /:/  /     \::::/__/    \:\__\       \:\/:/  /
    \:\__\        \:\__\         /:/  /       ~~~~         \/__/        \::/  /
     \/__/         \/__/         \/__/                                   \/__/

clavis

Powerful enhancements for Claude Code — unlock the full potential of your AI coding assistant.

npm version license

Installation

One-time use (no install needed)

npx @sriram-rach/clavis

Global install

npm install -g @sriram-rach/clavis

Then run clavis in any repo.

Local install (per-project)

npm install --save-dev @sriram-rach/clavis

Then run via npx or add it to your npm scripts:

{
  "scripts": {
    "setup-claude": "clavis"
  }
}

Features

Context Usage Statusline

A real-time statusline that shows you the active model, current task, working directory, session time, and context usage at a glance — with a color-coded progress bar that shifts from green to red as context fills up.

Tool Call Tracking

Tracks the number of tool calls made during a session and the last tool used, displayed live in the statusline (e.g. ⚙ 12 Edit).

Session Cost

Shows the approximate running cost of the current session in the statusline (e.g. ~$0.0142), calculated from token usage across all turns. Rates are sourced from the LiteLLM pricing registry and cached locally for 24 hours — they may not always reflect Anthropic's latest published prices.

Auto-Update

Clavis automatically checks for updates at the start of each Claude Code session and silently updates hooks in the background — no manual intervention needed.

How It Works

Running npx @sriram-rach/clavis in your repo root will:

  1. Create .claude/hooks/statusline.js — the statusline hook
  2. Add a statusLine entry to .claude/settings.json — tells Claude Code to use it
  3. Optionally create .claude/hooks/clavis-track-tools.js — the tool tracking hook
  4. Optionally add a PostToolUse entry to .claude/settings.json — enables tool tracking

It's idempotent — running it again skips any settings already configured.

Uninstall

Delete the hooks and remove the settings entries:

rm .claude/hooks/statusline.js
rm .claude/hooks/clavis-track-tools.js  # if tool tracking was enabled

Then remove the "statusLine" key and the PostToolUse hook entry from .claude/settings.json.

Contributing

Contributions are welcome! Please open an issue or submit a pull request.

License

MIT — see the LICENSE file for details.