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

@otixe/pi-cache-estable

v0.1.0

Published

Keep tool order steady and request longer retention so avoidable schema churn stops breaking the prompt-cache prefix

Readme

@otixe/pi-cache-estable

Your tools are the same, but their schemas keep moving around and breaking the prompt prefix. Keep tool order steady and request longer cache retention from supported providers, without changing which tools the agent can use.

Español · MIT

Problems it removes

  • Reordered schemas breaking a stable prefix → checked canonical tool ordering.
  • Short default retention → opt-in long-retention preference.
  • Configuration/runtime tool drift → best-effort coherence diagnostics.

Schema churn becomes a stable prompt prefix

Install in one command

From a reviewed local checkout:

pi install ./packages/pi-cache-estable

Configuration

Installing sets PI_CACHE_RETENTION=long only if it is unset. Preserve/set PI_CACHE_RETENTION=short to choose short retention, or PI_CACHE_ESTABLE_RETENTION for the package default.

Optional .pi/tools-order.json:

{"version":1,"priority":["read","bash","edit","write","plan_*"],"unlisted":"alphabetical"}

The checked AgentSession adapter targets Pi 1.4.0; unsupported hosts fail with TOOLS_ORDER_UNSUPPORTED_HOST. Missing/invalid order configuration is transparent. Avoid unnecessary membership changes even when ordering is stable.

Validation and rollback

To remove, pi remove SOURCE, then reload/restart your test session; preserve logs, snapshots and sessions.

Full monorepo configuration and reproducible validation: README, VALIDATION.

Security & limits

Provider support, pricing and cache hits vary; no fixed TTL, savings or hit rate are guaranteed. The adapter preserves membership and cannot grant permissions. Diagnostics never authenticate declared agent names. Stable ordering is not a security sandbox or proof of a cache hit.

Validated on Pi 1.4.0; the five host packages are peerDependencies "*", never bundled copies. Wildcard peers do not promise every host version. Review source/trust before installation: extensions run with process permissions. Tests use model/backend doubles and do not certify production authentication.

For local archives, extract the tarball and install its package directory: Pi 1.4.0 does not load .tgz extension sources even when pi install succeeds. The literal install exits 0; print/load exits 1. The monorepo README shows the supported extraction command.

Registry installation uses pi install npm:@otixe/[email protected] once the publisher releases that version. npm sources and repository/gallery URLs require separately authorized publication; a local checkout does not make them available.