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

pi-session-timer

v1.0.1

Published

Per-run stats for the Pi coding agent: wall-clock time, net tokens, and system-prompt footprint (first-message usage.input), live in the status row.

Readme

pi-session-timer

A Pi coding agent extension that tracks per-run stats: how long Pi spent working and how many tokens it consumed, live in a widget below the input editor.

⏱ run 03:12 · 48.5K tok        (while working)
⏱ last run 03:12 · 48.5K tok   (after it finishes)

Why per-run?

Pi's built-in status line already shows session-level active/total tokens. This widget answers a different question: what did this one message cost? Each time you send a message, the counters reset, tick live while Pi works, and freeze at the final values when the run completes.

  • run — wall time of the current agent run
  • tok — net tokens for the run (input + cacheRead + cacheWrite + output), summed from the assistant message usage fields

Reset is armed by your message and applied when the next agent run actually starts, so auto-retries and auto-compaction within one answer don't wipe the counters.

Install

From npm (published as pi-session-timer):

pi install pi-session-timer

Or from GitHub:

pi install github:stanleytejakusuma/pi-session-timer

Or clone into your extension directory:

git clone https://github.com/stanleytejakusuma/pi-session-timer \
  ~/.pi/agent/git/github.com/stanleytejakusuma/pi-session-timer

Then /reload in Pi.

How it works

One self-contained TypeScript file, zero dependencies. It subscribes to Pi's lifecycle events:

| Event | Role | |---|---| | session_start | reset counters | | message_start (role=user) | arm the reset for the next run | | agent_start / agent_end | track running time (depth counter handles subagents/retries) | | message_end (role=assistant) | accumulate token usage | | session_shutdown | stop the 1s refresh timer |

The widget is rendered via ctx.ui.setWidget with placement: "belowEditor".

License

MIT