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

cmux-captain

v0.4.0

Published

Drive a fleet of cmux worktrees through the SDLC, live — from Linear ticket to PR-ready

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

mblodemblode

Keywords

captainclicmuxgitlinearorchestrationworktree

Readme

captain

Captain a fleet of cmux worktrees from one Claude Code session, one worktree per Linear ticket.

Each worktree runs its own agent on a brief covering the whole job: plan, implement, review, open a PR. From your captain session you watch them all with captain status, approve their plans, and answer what they're blocked on. The child agents do the work; you steer.

Requirements

  • Node.js >= 22
  • git, claude (Claude Code), and cmux on your PATH
  • LINEAR_API_KEY (optional, pulls ticket details and screenshots into each brief)

Install

npm i -g cmux-captain                 # the CLI
npx skills add mblode/captain -g      # the captain skill
npx skills add mblode/agent-skills -g # the PR skills the brief runs
captain doctor                        # check your setup

Use

captain start TIG-430 TIG-431         # Linear issues → one worktree + agent each
captain start "tidy the README"       # a free-form task, no Linear, current dir
captain status                        # what's blocked, in flight, and ready
captain approve tig-430               # or: captain approve all
captain reject tig-431 --note "don't touch auth"

captain --help lists every command and flag.

How agents finish

Each worktree gets a definition of done (.captain/rubric.md, from the Linear issue). The agent runs a verifier against it and writes a verdict: a pass shows READY TO MERGE, a fail shows NEEDS YOU. Verified learnings are saved per repo and fed into the next brief.

Development

npm run build      # tsdown → dist/
npm run test       # vitest
npm run typecheck  # tsc --noEmit
npm run check      # ultracite (lint + format)

License

MIT