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

@voltade/volty

v0.1.6

Published

Remote CLI for the Volty platform — run operations, trigger real agent wakes, and inspect LLM I/O over an API key.

Readme

@voltade/volty

The Volty command-line tool for Claude Code. You set it up once; after that, you don't use it directly — Claude does. It lets Claude test the Volty agent for real (safely, in a sandbox — nothing ever reaches a real customer) and look inside what the agent saw and decided.

One-time setup

Open a terminal and run these four steps.

1. Install Bun (skip if you already have it):

curl -fsSL https://bun.sh/install | bash

Then close and reopen your terminal.

2. Install the Volty tool:

bun add -g @voltade/volty

3. Teach Claude Code how to use it:

volty skill install

4. Log in — this opens your browser; approve it with your normal Volty account:

volty auth login --env prod

To check it worked: volty auth whoami --env prod should print your email, org, and role.

That's it. You never need to memorize any other commands.

Using it — just ask Claude

Open Claude Code anywhere and ask in plain language. The skill you installed in step 3 kicks in automatically. For example:

  • "Test the Volty agent — ask it whether we're GST registered."
  • "Send the agent a follow-up in that same test conversation."
  • "What did the agent actually reply with, and why? Show me what the LLM decided."
  • "Why didn't the agent learn anything from that conversation?"
  • "Clean up the test conversations on prod."

Claude knows the safety rules: tests run against a sandboxed draft version of the agent with a synthetic contact, so nothing can ever be sent to a real customer, and Claude cleans up after itself when it's done.

Upgrading

When a newer version exists, the tool prints a notice — Claude will see it and upgrade for you. To do it yourself:

bun add -g @voltade/volty@latest && volty skill install