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

agentspend-cli

v0.1.0

Published

Track and cap AI agent API spend, and sync agent config/state across environments

Readme

agentspend

Track and cap AI agent API spend, and sync agent config/state across environments.

npm version build License: MIT

Local-first, free CLI. No server, no account — everything lives in ~/.agentspend (or $AGENTSPEND_HOME if set).

agentspend stats

Real numbers, not a benchmark — agentspend doesn't have a retrieval/accuracy metric to report, so this is test count, package size, and dependency count, regenerated from an actual build/test run by scripts/refresh-stats.mjs. See docs-vp/guide/stats.md for details.

Try it now

npx agentspend-cli spend track --provider openai --cost 0.42
npx agentspend-cli spend report

Install

npm install -g agentspend-cli

The package on npm is agentspend-cli; the command it installs is agentspend.

What agentspend solves

  • No visibility into agent API cost — spend track records each call's cost by provider and project; spend report totals it.
  • Budgets get blown silently — spend budget <amount> sets a cap; spend budget (no argument) checks status and exits non-zero when over, so it can gate a CI job.
  • Agent config/memory drifts across machines — sync save/sync load snapshots a config or state file under a named profile you can restore anywhere.

Usage

spend

agentspend spend track --provider openai --model gpt-4o --cost 0.42 --project myagent
agentspend spend track --provider anthropic --cost 0.10 --project myagent

agentspend spend report                    # totals across all entries
agentspend spend report --project myagent  # scoped to one project
agentspend spend report --json             # machine-readable output

agentspend spend budget 10.00              # set a $10 budget
agentspend spend budget                    # check status; exits 1 if over budget

sync

agentspend sync save myagent ./agent-config.json    # snapshot a file as "myagent"
agentspend sync load myagent ./restored-config.json # restore it elsewhere
agentspend sync list                                # list saved profiles

Develop

pnpm install
pnpm dev -- spend track --provider openai --cost 0.42
pnpm typecheck
pnpm test

App code lives in src/logic/; the CLI wiring is in src/cli.ts.

Release

pnpm changeset        # describe your change
git commit -am "..."  # commit the changeset file

Merging to main triggers the deploy-npm-publish GitHub Actions workflow (Changesets opens a "Version Packages" PR; merging that publishes). Requires an NPM_TOKEN secret.

Docs

Contributing

See CONTRIBUTING.md. Please also review our Code of Conduct and Security Policy.

License

MIT © Manoj Mallick