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

@samuelfaj/distill

v1.5.2

Published

Compress command output for downstream LLMs.

Readme

@samuelfaj/distill

Install:

npm i -g @samuelfaj/distill

Run onboarding:

distill

After onboarding, use /distill in Claude/Codex to make the agent keep talking in distill language for the whole thread. It should adopt the language style, not return your prompt rewritten.

Default response shape uses Military English + AR-0/AR-1 atoms with fixed prefixes:

Dict: S=state C=context D=action R=risk O=outcome N=no-go P=proof
S glab auth fail gitlab.com
D inspect remotes + MR meta
R merge/update may block w/o token

Inline variables use dynamic <term>=#<letter><digit> assignments chosen by the model from repeated terms. They stay thread-local unless distill dsl learn-thread --stdin sees the explicit variable more than 5 times; learned entries are removed when absent from the next learned thread.

/distill also has DSL memory:

distill dsl show
distill dsl show --candidates
distill dsl learn --dry-run "Dict+: A1=authentication fix"
distill dsl learn-thread --stdin --dry-run < transcript.txt
distill dsl promote --dry-run
distill dsl add alias A1 "authentication bug fix" --scope project
distill dsl prune --dry-run

Normal runs load compact active DSL memory into the prompt. Reusable Dict+ entries from /distill output are learned as project candidates using the shortest available key and can later be promoted with distill dsl promote.

At thread end, pipe a transcript into distill dsl learn-thread --stdin. It learns repeated workflow language as candidates after reviewer approval and sensitive-term filtering.

You can also pipe command output into distill:

bun test 2>&1 | distill "Did tests pass? Return PASS or FAIL, followed by failing test names if any."
git diff | distill "What changed? Return only files changed and one-line summary for each."