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

@lbsa71/granules

v1.0.20

Published

Minimal multi-agent orchestrator using MCP

Readme

GRANULES

Minimal multi-agent orchestrator. An MCP server holds work items (granules). Claude Code CLI instances act as workers that claim and complete granules.

Design Principles

  • Self-building: GRANULES bootstraps itself - the first worker plans, subsequent workers implement
  • Atomic claims: Only one worker can claim a granule; claim fails if already taken
  • Summaries enable coordination: Completed granules include summaries so workers can understand prior work

Architecture

┌─────────────┐      ┌─────────────┐
│ Orchestrator│──────│ MCP Server  │
│   (loop)    │      │ (in-memory) │
└──────┬──────┘      └──────┬──────┘
       │                    │
       │ spawns             │ tools
       ▼                    ▼
┌─────────────┐      ┌─────────────┐
│  Worker W-1 │─────▶│  Worker W-2 │ ...
│ (claude cli)│      │ (claude cli)│
└─────────────┘      └─────────────┘

Granule Classes

| Class | Purpose | |-------|---------| | explore | Understand codebase/context | | plan | Design implementation approach | | implement | Write/modify code (artifacts) | | test | Write or run tests | | review | Critique another worker's output | | consolidate | Merge work from multiple workers | | audit | Deferred architectural review |

Quick Start

# Run with npx (no installation)
npx @lbsa71/granules

# Or with a specific task
npx @lbsa71/granules -p "Add dark mode support"

Project Structure

granules/
├── src/
│   ├── index.ts         # Entry point
│   ├── orchestrator.ts  # Main loop, worker spawning
│   ├── server.ts        # MCP server setup
│   ├── store.ts         # In-memory granule store
│   ├── types.ts         # Type definitions
│   ├── worker.ts        # Worker spawning, CLASS_PROMPTS
│   ├── ui.ts            # Terminal UI
│   ├── session-log.ts   # Session logging
│   ├── tools/           # MCP tool implementations
│   └── *.test.ts        # Tests
├── docs/                # Detailed documentation
├── logs/                # Worker output logs
└── mcp-config.json      # MCP server config

Documentation

CI/CD

  • CI: Tests and build run automatically on all pull requests and pushes to main
  • Publish: The package @lbsa71/granules is automatically published to npm on every push to main. Add NPM_TOKEN secret to GitHub repository settings.