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

agent0-cli

v2.2.1

Published

Command-line interface for agent0 — manage agents, prompt versions, runs, tags, providers, and MCP servers from a shell.

Readme

agent0-cli

Command-line interface for agent0 — the open-source platform for building, running, and monitoring AI agents. Lets you (and AI coding tools like Claude Code, Cursor, and Codex) manage agents, prompt versions, runs, tags, providers, and MCP servers from a shell.

Install

npm install -g agent0-cli

The package installs an agent0 binary. Requires Node 20+.

Quick start

# Sign in to a deployment (prompts for URL + personal access token)
agent0 login

# List your agents
agent0 agents list

# Pull a prompt, edit it, push a new version, deploy to staging
agent0 prompt pull <agentId> -o prompt.json
# ... edit prompt.json ...
agent0 prompt push <agentId> -f prompt.json --deploy staging

# Run an agent
agent0 run <agentId> --input "..."

# Inspect failed runs
agent0 runs list --status failed
agent0 runs get <runId>

Authentication

The CLI uses personal access tokens (PATs), bound to your user. Mint one at:

<your-agent0-url>/account/personal-access-tokens

Tokens start with agent0_pat_. They inherit your role in whichever workspace each request targets.

API keys (x-api-key) are accepted at runtime for read/run flows, but agent0 login is PAT-only — keys can't bootstrap a profile.

Profiles

Config lives at ~/.config/agent0/config.json (mode 0600). It supports multiple deployments (cloud, self-hosted, etc.):

{
  "active": "default",
  "profiles": {
    "default":  { "url": "https://...", "token": "agent0_pat_...", "workspace_id": "ws_..." },
    "selfhost": { "url": "https://agent0.acme.internal", "token": "...", "workspace_id": "..." }
  }
}

Resolution order for each field: explicit flag (--profile, --url, --workspace) → env (AGENT0_PROFILE, AGENT0_URL, AGENT0_TOKEN, AGENT0_WORKSPACE) → active profile in config.

agent0 use <profile>          # Switch active profile
agent0 whoami                 # Show signed-in identity
agent0 logout                 # Revoke token + remove profile
agent0 workspaces list        # Show every workspace your PAT can act in
agent0 workspaces use <id>    # Change active workspace on this profile

Commands

agents       list | get <id> | create --name ... | rename <id> --name ...
prompt       pull <agentId> [--version-id <id>] [--env staging|production] [-o file]
             push <agentId> -f file [--deploy staging|production]
versions     list <agentId> | get <agentId> <versionId>
             deploy <agentId> <versionId> --env staging|production
run          <agentId> --input "..." [--env staging|production] [--var key=val]...
runs         list [--agent <id>] [--status success|failed] [--from <iso>] [--to <iso>]
             get <runId>
tags         list | create --name ... --color "#..." | delete <id>
providers    list
mcps         list | refresh <id>
workspaces   list | use <id>

Add --json to any read command for raw JSON output (also the default when stdout is not a TTY, so commands pipe cleanly).

Output

  • TTY: aligned plain-text rendering for easy human scanning.
  • Non-TTY or --json: JSON payload (compact when piped, pretty when forced with --json).

License

ISC