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

tokenking

v1.3.6

Published

Analyze Claude Code token usage for a specific project

Readme

TokenKing

npm version npm downloads GitHub Release CI/Release Node.js Version License: MIT

A simple CLI tool that shows how much Claude Code usage a specific project has consumed.

What it does

Analyzes your Claude Code session history and shows aggregated statistics for a specific project:

  • Total sessions and date range
  • Token usage (input, output, cache creation/read)
  • Models used
  • Estimated costs in USD

Requirements

  • Node.js >= 18

Installation

# Install globally
npm install -g tokenking

# Or use with npx (no installation required)
npx tokenking ~/src/my-project

Usage

# Analyze current directory
tokenking .

# Analyze specific project
tokenking ~/src/my-project

# Show help
tokenking --help

# Show version
tokenking --version

# Or use with npx
npx tokenking ~/src/my-project

Example Output

📊 TokenKing Report
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Project: /path/to/my-project

Sessions: 12
First Session: 2025-10-15
Last Session: 2025-11-06
Date Range: 22 days

Total Tokens: 2,450,789
  Input: 1,234,567 tokens
  Output: 456,789 tokens
  Cache Create: 234,567 tokens
  Cache Read: 524,866 tokens

Models Used:
  • claude-sonnet-4-5-20250929
  • claude-haiku-4-5-20251001

Estimated Cost: $45.67 USD

How it works

TokenKing is built with TypeScript and uses ccusage as a dependency to read Claude Code session data. It loads all sessions, filters by project path (with support for moved directories via basename matching), then aggregates and displays the results.

Dependencies

  • ccusage - Reads Claude Code session data from ~/.claude/projects/
  • picocolors - Terminal colors for output formatting