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

clawpipe

v0.1.5

Published

Talk to your OpenClaw agent from the terminal — with file and folder context.

Readme

clawpipe

Talk to your AI agent from the terminal. Pass files as context with @. That's it.

npm

npm i -g clawpipe

Why

You're in the terminal. You want to ask your agent something about the code you're staring at. You don't want to copy-paste into a chat window, attach files manually, or leave your workflow.

clawpipe "why is this failing?" @tests/auth.test.ts

Done. File contents included. Response in your terminal.

Examples

# Ask about a file
clawpipe "explain this" @src/index.ts

# Review a diff
git diff | clawpipe "review this"

# Combine piped input with file context
git diff | clawpipe "review against the spec" @docs/spec.md

# Include a whole directory
clawpipe "what does this project do?" @src/

# Script it
clawpipe --raw "summarize @README.md" | pbcopy

@ references

@path resolves relative to your cwd. Directories include a file listing + contents of text files.

@file.ts       # file contents
@src/          # directory listing + text files
@../spec.md    # relative paths work

Tab completion works out of the box (bash/zsh/fish):

# Install completions
clawpipe --completions zsh >> ~/.zshrc   # or bash/fish

Options

-s, --session <id>    Target a specific agent session (default: main)
-r, --raw             No colors, no spinner — for piping
-m, --model <model>   Override the model
-V, --version         Version

Setup

Requires OpenClaw with the gateway running.

openclaw gateway start

License

MIT