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

@chasehelton/orcastrator

v0.8.2

Published

Lightweight CLI-first multi-agent coding runtime built on GitHub Copilot SDK

Readme

🐋 Orcastrator

Lightweight CLI-first multi-agent coding runtime built on GitHub Copilot SDK.

Inspired by bradygaster/squad, stripped down to the essentials.

Quick Start

# Initialize in your project (analyzes repo via Copilot to generate tailored agents)
npx orcastrator init

# Or use the default template without Copilot
npx orcastrator init --default

# Customize your agents
vim orcastrator.config.ts

# Generate agent charters
npx orcastrator build

# Run an ad-hoc task
npx orcastrator run "build the login page"

# Work on a GitHub issue
npx orcastrator issue 42

# Work on a Linear issue (auto-detected from identifier format)
npx orcastrator issue ENG-123

# List open issues (auto-detects provider from config)
npx orcastrator list

How It Works

  1. Define agentsorcastrator init scans your repo and uses Copilot to generate a tailored agent team in orcastrator.config.ts
  2. Build charters — config generates markdown files in .orcastrator/ that become system prompts
  3. Route tasks — pattern matching routes your task to the right agent(s)
  4. Fan out — multi-agent tasks run in parallel via Promise.allSettled
  5. Learn — decisions and history are logged to .orcastrator/ and committed to git

CLI Commands

| Command | Description | |---------|-------------| | orcastrator init | Scaffold config with Copilot-powered agent generation | | orcastrator init --default | Scaffold config with default agent template | | orcastrator build | Generate markdown from config | | orcastrator run "<task>" | Execute an ad-hoc task | | orcastrator issue <number> | Work on a GitHub issue (e.g. 42) | | orcastrator issue <identifier> | Work on a Linear issue (e.g. ENG-123) | | orcastrator list | List open issues (Linear or GitHub) | | orcastrator list --provider linear --team ENG | List open Linear issues for a team | | orcastrator list --mine | List issues assigned to you | | orcastrator status | Show agents, routing, and recent sessions | | orcastrator agents list | List configured agents |

The issue provider is auto-detected: identifiers like ENG-123 route to Linear; plain numbers like 42 route to GitHub. Use --provider to override.

Config

import { defineOrcastrator, defineAgent, defineRouting } from "orcastrator";

export default defineOrcastrator({
  name: "my-project",
  defaultModel: "claude-sonnet-4.6",

  agents: [
    defineAgent({
      name: "architect",
      role: "System Architect",
      expertise: ["system design", "API design"],
      model: "claude-opus-4.6",
      instructions: "You design clean, scalable systems.",
    }),
    defineAgent({
      name: "builder",
      role: "Implementation Engineer",
      expertise: ["TypeScript", "React", "Next.js"],
      instructions: "You write production-quality code with tests.",
    }),
  ],

  routing: defineRouting({
    rules: [
      { pattern: /design|architect/, agents: ["architect"] },
      { pattern: /build|implement|fix/, agents: ["builder"] },
    ],
    defaultAgent: "builder",
  }),

  // Optional: configure Linear integration
  linear: {
    // Defaults to LINEAR_API_KEY env var — prefer the env var to avoid committing secrets
    // apiKey: "lin_api_...",
    defaultTeam: "ENG",  // Used by `orcastrator list` when no --team flag is given
  },
});

Linear setup

  1. Generate a personal API key at linear.app/settings/account/security
  2. Set it as an environment variable: export LINEAR_API_KEY=lin_api_...
  3. Optionally add linear: { defaultTeam: "ENG" } to your config for orcastrator list filtering

When working on a Linear issue, orcastrator will automatically:

  • Mark the issue In Progress when work starts
  • Post a PR comment and mark the issue In Review when a PR is created (--pr flag)

Architecture

User (CLI)
    │
    ▼
┌──────────────────────────────────┐
│           Coordinator            │
│  Route → Spawn → Execute → Log  │
└──────────┬───────────────────────┘
           │
           ▼
┌──────────────────────────────────┐
│    Agent Lifecycle Manager       │
│  Charter compile → Session       │
│  create → Send task → Collect    │
└──────────┬───────────────────────┘
           │
           ▼
┌──────────────────────────────────┐
│      GitHub Copilot SDK          │
└──────────────────────────────────┘

Requirements

  • Node.js ≥ 22.0.0
  • gh CLI (for GitHub issue/PR commands)
  • GitHub Copilot access (authenticated via gh auth login)
  • LINEAR_API_KEY env var (for Linear issue workflows)

License

MIT