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

@pi-lab/subagent

v1.0.0

Published

Minimal synchronous parallel subagent tool for pi coding agent

Readme

@pi-lab/subagent

A minimal synchronous subagent extension for pi.

Install

pi install npm:@pi-lab/subagent

Features

  • Schema only — no system-prompt injection
  • No role files — no *.md specialists. The child uses the same model, tools, and project conventions as the main agent
  • Simple lifecycle — one prompt per call; parallel execution uses Pi's native tool concurrency
  • Trigger policy is yours — this tool does not tell the model when to delegate. It follows whatever you define

Use when

Isolate context. Add no orchestrator.
You need a tool that just isolates context, not an orchestrator.

Wrap headless pi.
You only want a thin wrapper around headless pi.

One config for parent and child.
The child behaves like the parent. No extra implicit instructions.

Not for

Reusable roles, async/steer/fleet, or a workflow DSL. If you need these features, use a larger extension.