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

@agent-dev/agentdev

v1.4.1

Published

Hierarchical agent orchestration on herdr — a pi extension (the brain) driving herdr (the body).

Readme

agentdev

A pi extension that runs a small crew of coding agents on top of herdr. You give it a goal. It plans with you, then dispatches workers that build, test and review the work until it is clean and ready for you to approve the commits. Every agent runs in its own herdr pane, so you can watch what is happening and jump in whenever you want.

Quick start

Install the launcher once, then just type agentdev:

npm i -g @agent-dev/agentdev
agentdev

The first launch installs whatever is missing. herdr goes in first, then pi, then the extension itself, and the herdr server is started if it isn't running. After that, pi opens with the crew already on. If pi asks you to log in to a model provider, you do that once and you're set.

No global install? The same flow works through npx:

npx @agent-dev/agentdev install
npx @agent-dev/agentdev

Or from a clone:

git clone https://github.com/dozeotarios/agent-dev
cd agentdev
./setup.sh

What happens after you give it a goal

The first part is shared with you. The leader checks the repository (or helps you pick a stack for a new one), builds a small glossary of the domain, runs a risk interview, and asks which project mode you want.

Then the autopilot takes over. A consensus loop with a Planner, an Architect, a Developer and a Critic produces a plan. The plan is sliced into stories, and each story gets its own git worktree and a Subworker. Once the code builds and the tests pass, six reviewers look at it from different angles: code quality, efficiency, security, API shape, reliability and domain. The loop keeps going until nothing actionable is left.

Then everything stops. Nothing gets committed until you confirm, unless you chose +yolo, which commits on its own.

Commands

Inside pi, with the crew on:

  1. /agentdev on turns the crew on. Every message becomes a goal.
  2. /agentdev status shows the goals and where each one is.
  3. /agentdev confirm <goal> accepts the commit-ready gate, so the commits actually happen.
  4. /agentdev resume picks the work back up after a restart.

The launcher also understands agentdev doctor (the state of your setup), agentdev install, and agentdev version.

Project modes

direct-PR is the default: stop at commit-ready, commit on confirm. The others are no-mistakes, local-only, and +yolo (auto-commits).

More

Full instructions: INSTRUCTIONS.md

Design and acceptance criteria: ARCHITECTURE.md, specs/acceptance-criteria.md

Development notes: DEVELOPMENT.md

Works on Linux, WSL and Windows.