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

@prom.codes/saver

v0.3.0

Published

prom.codes Saver — cut token cost without cutting quality, as an MCP installer.

Readme

@prom.codes/saver

prom.codes Saver — cut token cost without cutting quality. A tiny, pure-JS MCP installer (stdio): one setup tool writes an efficient-output rule block into your agent's runtime configs so it spends fewer tokens on its own prose — preamble, play-by-play narration, pasted tool output — while keeping code, caveats and destructive sequences verbatim.

It is the third prom.codes tool, alongside prom.codes Context (code retrieval) and prom.codes Memory (agent memory).

Quick start (Claude Code)

claude mcp add saver -- npx -y @prom.codes/saver@latest

No key needed. claude mcp add defaults to local scope; add --scope project for a committable .mcp.json. Other hosts (Cursor, VS Code) use the same command/args in their own config.

Then ask your agent to run setup once per workspace. Levels: lite (filler only), balanced (default — lean, not terse), aggressive (telegraphic, opt-in, never for code/destructive work). The rules keep code, caveats, destructive steps and anything the agent needs later verbatim — it shapes phrasing, never what the agent does or remembers.

It installs itself. An MCP server can't act on its own, so the rule only saves tokens once it's in a config file. On startup the Saver auto-installs the marked rule block into config files you already have (CLAUDE.md / AGENTS.md / Cursor / Augment) — idempotent, never creates a new file, skipped for home/root, opt out with PROMETHEUS_SAVER_AUTO_SETUP=off. Run setup to install into all runtimes (incl. creating AGENTS.md if you have none). A status tool reports where it writes, the key state, which runtimes already have the block, and whether a newer version is published.

No database and no native modules — npx works turnkey everywhere (Node ≥ 20.10). The workspace is auto-detected (Claude Code CLAUDE_PROJECT_DIR); set PROMETHEUS_WORKSPACE_ROOT only to target a different folder. An API key is optional: the Saver works fully without one, and accepts the same PROMETHEUS_API_KEY (prom_live_<tag>_<secret>) as prom.codes Context and Memory to tie the install to your account.

Docs: https://prom.codes/docs/mcp/saver