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-moa-subagents

v0.1.1

Published

Mixture-of-experts bug diagnosis for Pi

Readme

pi-moa-subagents

Mixture-of-experts bug diagnosis for Pi. Point multiple models at a bug, have each investigate independently, then synthesize findings into an executive summary or an implemented-and-tested fix.

Prerequisites

This extension requires pi-subagents. Install it first:

pi install npm:pi-subagents

pi-moa-subagents does not bundle pi-subagents — it uses its subagent tool as the execution engine. If you try to run /moa-subagents without it, you'll get a clear error with installation instructions.

Installation

pi install npm:pi-moa-subagents

Or install from a local path during development:

pi install /absolute/path/to/pi-moa-subagents

How It Works

  1. You describe the bug (inline or multi-line editor).
  2. You select 1+ investigator models (multi-select) — each gets run sequentially via subagent concurrency: 1 to respect single-GPU VRAM limits. Investigators are read-only by instruction (tools: read, grep, find, bash).
  3. You pick a synthesis model (single select) that consolidates findings.
  4. You choose summary-only or auto-implement-and-test.

Investigators write reports to diagnose/<timestamp>/ as .md files. The synthesis step reads these and either:

  • Summary mode: Produces root cause, confidence, evidence per model, and a recommended fix direction. Nothing is changed in the codebase.
  • Implement mode: Hands off to the built-in worker agent with an acceptance contract requiring tests to pass before finishing.

Usage

With inline description

/moa-subagents The login form crashes when a user enters special characters in the email field

With multi-line editor (bare invocation)

/moa-subagents

Opens a text editor for a detailed bug description including steps to reproduce, expected vs. actual behavior, etc.

Architecture Notes

  • Sequential model loading. Uses concurrency: 1 on the investigator batch — models run one at a time so only one local model occupies VRAM at once.
  • Investigators are read-only by instruction. The investigator agent has read, grep, find, and bash tools (no edit/write), plus an explicit system prompt not to modify files. Since bash is included, a model could technically write via shell redirection if it ignored instructions — this is enforced by convention, not hard sandboxing.
  • Agent file. The investigator.md agent definition ships in the package source and is copied to ~/.pi/agent/agents/investigator.md (or $PI_CODING_AGENT_DIR/agents/) on first session start. Existing customizations at that path are never overwritten.

License

MIT