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

warroom

v0.2.0

Published

5 AI agents enter the war room. They debate, build, and review your code. The conversation is the product.

Readme

warroom

5 AI agents enter the war room.

They debate, build, and review your code.

npm CI license


Give it a task. Five agents argue about the design, implement it, review each other's work, and try to break it. You get finished code and a conversation showing exactly how they got there.

  warroom
  5 agents. 1 task. Let the debate begin.

  Task: Add a hello world Express server

  ────────────────────────────────────────────
  Phase 1: Design
  ────────────────────────────────────────────
  [ARC] Architect  I propose splitting server.js from index.js. The app...
  [CHL] Challenger  Two real issues. No "main" in package.json -- npm st...
  [ARC] Architect  Both valid. Adding start script, main field, and err...
  [CHL] Challenger  Design approved. Error handling on the server instan...

  ────────────────────────────────────────────
  Phase 2: Build
  ────────────────────────────────────────────
  [BLD] Builder  Implemented. 4 files. server.js exports app without...
  4 files written

  ────────────────────────────────────────────
  Phase 3: Review
  ────────────────────────────────────────────
  [REV] Reviewer  LGTM. server.js/index.js split is correct. Error han...
  [BRK] Breaker  Two real bugs. PORT=0 reports "port 0" instead of ac...

  DONE

  5 agents · 6 messages · 1 revision · 2 bugs caught · 4 files · 70s

Install

Claude Code plugin (recommended)

claude plugin marketplace add https://github.com/Djsand/warroom
claude plugin install warroom

Then:

/warroom "Add user authentication with OAuth"

No API key needed. Uses your Claude Code subscription.

Standalone CLI

npx warroom setup --token $(claude setup-token)
npx warroom run "Add user authentication with OAuth"

Or with an API key:

export ANTHROPIC_API_KEY=sk-ant-...
npx warroom run "Add user authentication with OAuth"

How it works

         ┌─────────────┐
         │  Your task   │
         └──────┬───────┘
                │
    ┌───────────▼───────────┐
    │   Phase 1: DESIGN     │  Architect proposes.
    │   Architect + Challenger  Challenger attacks.
    │   debate 2-4 rounds   │  They revise until
    │                       │  the design holds.
    └───────────┬───────────┘
                │
    ┌───────────▼───────────┐
    │   Phase 2: BUILD      │  Builder implements
    │   Builder writes code │  the agreed design.
    └───────────┬───────────┘
                │
    ┌───────────▼───────────┐
    │   Phase 3: REVIEW     │  Reviewer checks quality.
    │   Reviewer + Breaker  │  Breaker tries to
    │   examine the code    │  break everything.
    └───────────┬───────────┘
                │
    ┌───────────▼───────────┐
    │   Phase 4: FINALIZE   │  conversation.md
    │   Save conversation   │  summary.md
    │   and summary         │  code on branch
    └───────────────────────┘

The 5 Agents

| Agent | Tag | What it does | Optimizes for | |-------|-----|-------------|---------------| | Architect | ARC | Proposes designs, revises based on critique | Elegance and maintainability | | Challenger | CHL | Finds gaps and edge cases, attacks every proposal | Robustness and completeness | | Builder | BLD | Implements the agreed design | Simplicity and shipping | | Reviewer | REV | Reviews code for bugs and quality issues | Quality and best practices | | Breaker | BRK | Tries to break everything with adversarial tests | Finding failures |

Each agent has a different objective function. They genuinely disagree. That's what makes the conversations interesting.


What you get

.warroom/conversations/
├── conversation.md    <- Full agent debate (shareable)
└── summary.md         <- What was built, decisions made, bugs caught

The conversation is the product. Screenshot it. Share it. Learn from it.


Commands

warroom run <task>       Assign a task to the agent team
warroom setup            Authenticate (setup token or API key)
warroom setup --login    Browser-based OAuth login
warroom read             Read the latest conversation
warroom read --format html   Export as standalone HTML
warroom status           List all conversations

Auth (standalone only)

The plugin mode needs no configuration.

# Use your Claude subscription (recommended)
warroom setup --token <paste from `claude setup-token`>

# Or use an API key
export ANTHROPIC_API_KEY=sk-ant-...

Examples

Real conversations from warroom sessions — each one shows the agents debating, catching bugs, and refining code:

Want to add your own? See CONTRIBUTING.md.


License

MIT