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

@jununfly/zj-loop-cost

v0.1.5

Published

Estimate token budgets and daily costs for agentic loop working patterns. By cadence, readiness level (L1/L2/L3), and coding agent tool.

Readme

zj-loop-cost

Estimate daily token spend for agentic loop working patterns by cadence and readiness level (L1–L3).

Uses cost metadata from patterns/registry.yaml. When run with a project root, the project-local registry is preferred over the packaged default.

Install & Run

npx @jununfly/zj-loop-cost . --pattern ci-sweeper --cadence 15m --level L2
npx @jununfly/zj-loop-cost . --pattern daily-triage --level L1 --json
npx @jununfly/zj-loop-cost --registry patterns/registry.yaml --pattern daily-triage
npx @jununfly/zj-loop-cost --package-registry --pattern daily-triage
npx @jununfly/zj-loop-cost --list

If npx stalls on package resolution, use an installed binary or npm's local cache:

zj-loop-cost . --pattern daily-triage --level L1
npm exec --offline --package=@jununfly/zj-loop-cost -- zj-loop-cost . --pattern daily-triage --level L1

From this repo:

cd tools/zj-loop-cost
npm install
npm test

Options

| Flag | Description | |------|-------------| | --pattern | Pattern id (see --list) | | --registry | Explicit registry file | | --package-registry | Use packaged registry defaults first | | --cadence | Override cadence (e.g. 15m, 1d) | | --level | L1, L2, or L3 cost/readiness model (default L1) | | --conservative | Use slower cadence from ranges | | --json | Machine-readable output |

Scenarios

Each estimate includes:

  • Early-exit / no-op — empty watchlist, minimal tokens
  • Full triage — every run does a full scan
  • Action every run — implementer + verifier every time (worst case)
  • Realistic blend — level-based mix (documented in output)

Pair with zj-loop/zj-loop-budget.md (scaffolded by zj-loop-init) and zj-loop-audit cost observability checks.

Cost level is not execution authority. Route Table policy and pattern-specific guards decide whether a loop is report-only, request-only, dry-run, or live.

See docs/operating-loops.md.