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

@yusukeshib/pi-token-counter

v0.1.1

Published

Append each tool's own output token cost to its tool-use row, color-coded by size.

Readme

@yusukeshib/pi-token-counter

A pi extension that appends each tool's own output token cost to its tool-use row, color-coded by size. This is the tool's own contribution to the context (its result content) — not the cumulative total.

What it looks like

pi-token-counter in action

Each tool-use row gains a trailing token count, colored by how much it adds:

read src/main.rs                 +312 tok
$ npm test -- --watch=false      +1,840 tok
grep "TODO" src                  +6,204 tok

| Color | Meaning | Threshold | | ----------------- | -------------------------------- | --------------- | | blue (accent) | small output | < 1,000 tok | | yellow (warning) | medium output | < 5,000 tok | | red (error) | large output | >= 5,000 tok |

The token estimate uses the same heuristic as pi's built-in estimator (text characters / 4).

Install

pi install npm:@yusukeshib/pi-token-counter

Via git (no npm publish required):

pi install git:github.com/yusukeshib/pi-token-counter

Try it without installing:

pi -e npm:@yusukeshib/pi-token-counter

How it works

The tool_result event carries each tool's result content, so the extension estimates its tokens there and caches the value by toolCallId. It overrides only renderCall for the built-in tools (read / bash / edit / write / grep / find / ls) to append the colored token count — renderResult is left untouched so pi's built-in result rendering (diffs, syntax highlighting, etc.) is fully preserved. When a result arrives the row re-renders and renderCall reads the cached estimate.

License

MIT