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

@sisu-ai/mw-usage-tracker

v9.0.0

Published

Track token usage across your pipeline and estimate cost.

Downloads

27

Readme

@sisu-ai/mw-usage-tracker

Track token usage across your pipeline and estimate cost.

Tests CodeQL License Downloads PRs Welcome

Setup

npm i @sisu-ai/mw-usage-tracker

Usage

import { usageTracker } from '@sisu-ai/mw-usage-tracker';

const app = new Agent()
  .use(usageTracker({
    'openai:gpt-4o-mini': {
      // Preferred: prices per 1M tokens (matches provider docs)
      inputPer1M: 0.15,
      outputPer1M: 0.60,
      // Optional vision pricing (choose one):
      // a) Per 1K images (e.g., $0.217/K images)
      imagePer1K: 0.217,
      // b) Approximate per-1K "image tokens"
      // imageInputPer1K: 0.217,
      // imageTokenPerImage: 1000,
    },
    // Fallback default for other models
    '*': { inputPer1M: 0.15, outputPer1M: 0.60 },
  }, { logPerCall: true }))

How it works

  • Wraps ctx.model.generate for the duration of the pipeline.
  • Accumulates promptTokens, completionTokens, totalTokens from ModelResponse.usage.
  • If a price table is provided, computes costUSD per call and totals.
  • Optional: for vision models
    • Providers vary: some include image cost in native token usage; others bill separately per image.
    • If billed per image batch, set imagePer1K (e.g., 0.217 USD per 1K images). The tracker converts this to per-image.
    • Or configure imageInputPer1K + imageTokenPerImage to approximate per-1K image-token pricing. In that mode we split prompt tokens into estimated imageTokens = imageCount * imageTokenPerImage (default 1000) and textPromptTokens = promptTokens - imageTokens, then price them separately.
  • Writes totals to ctx.state.usage and logs them at the end.
  • Cost is rounded to 6 decimals to avoid showing small calls as 0.00.

Notes

  • Each adapter should map its native usage fields to ModelResponse.usage.
  • If a provider doesn’t return usage, you’ll get counts of calls only (no cost).
  • Image cost estimation is an approximation unless your adapter returns precise image token usage.

Community & Support

Discover what you can do through examples or documentation. Check it out at https://github.com/finger-gun/sisu. Example projects live under examples/ in the repo.