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

agcmd

v1.1.0

Published

CLI for routing messages to AI agents in tmux panes

Readme

agcmd

Agent Command Center CLI for routing messages between AI agents running in tmux panes. Includes injected instructions for repeated tasks.

Tmux window layout:

Prerequisites

  • Node.js >=22 (haven't tested on earlier versions)
  • tmux

Install

npm install -g agcmd

Quickstart

# inside a tmux window
agcmd start # splits the window into panes for each agent

agcmd claude send "review the auth module"
agcmd all send "sync up"

Agent-to-agent

An agent can ask another agent a question, and the other agent can respond.

agcmd ask codex auth-design "How should we handle token refresh?"
agcmd answer claude auth-design "Use refresh tokens with 7-day expiry"

Config

Config is stored at ~/.agcmd/config.json (created on first run). Minimal example:

{
  "agents": {
    "claude": { "command": "claude" },
    "codex": { "command": "codex" },
    "gemini": { "command": "gemini" }
  },
  "defaultReviewFormat": "JSON with agrees, confidence, blocking, review-comments",
  "log": false
}

Storage Layout

Data is isolated per-project and per-tmux-window:

~/.agcmd/
├── config.json                          # Global (shared across all projects)
└── projects/
    └── <slugified-path>/                # Per-project (e.g., code-agcmd)
        ├── plans/
        │   └── <feature>/
        │       └── <agent>.md
        ├── questions/
        │   └── <topic>/
        │       └── <agent>.md
        ├── logs/
        │   └── commands.jsonl
        └── sessions/
            └── <tmux-window-id>/        # Per-window (e.g., @0, @3)
                └── panes.json
  • Project path is derived from the git root, slugified relative to $HOME (e.g., ~/Code/agcmdcode-agcmd). Falls back to cwd if not in a git repo.
  • Session uses the tmux window ID so multiple windows can run independent agent sets. Falls back to default outside tmux.

Commands

  • agcmd start
  • agcmd <agent> send "..."
  • agcmd <agent> plan <feature> "..."
  • agcmd <agent> review <feature | diff> [--type code]
  • agcmd ask <to-agent> <topic> "..."
  • agcmd answer <to-agent> <topic> "..."