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

claudex-council

v1.7.0

Published

Orchestrate brainstorming between Claude Code and Codex CLI

Readme

ClaudexCouncil

Make LLMs debate so you don't have to.

ClaudexCouncil orchestrates brainstorming sessions between Claude Code and Codex CLI. One proposes, the other critiques, and they iterate until a refined answer emerges.

How it works

You → prompt → Claude (proposer) → Codex (critic) → Claude (refines) → ... → Final Synthesis

Each round, the proposer generates or improves ideas while the critic challenges them. After N rounds, Claude synthesizes everything into a final, consolidated answer.

Quick start

npx claudex-council "your prompt"

Install globally

npm install -g claudex-council

Prerequisites

Both CLI tools must be installed and authenticated:

Usage

# Basic — 3 rounds by default
claudex-council "How should I architect a distributed cache?"

# More rounds
claudex-council -r 5 "REST vs GraphQL for a mobile-first project?"

# See each round's response in real-time
claudex-council -v "Database migration strategies"

# Save the full transcript
claudex-council -s "Microservices vs monolith trade-offs"

# All options combined
claudex-council -r 5 -s -v -o ./my-transcripts "Your complex question here"

Options

| Flag | Default | Description | |------|---------|-------------| | -r, --rounds <n> | 3 | Number of exchange rounds (max 10) | | -s, --save-transcript | false | Save full transcript as markdown | | -o, --output <dir> | ./transcripts/ | Transcript output directory | | -v, --verbose | false | Show each round's response in real-time |

Example output

💡 Round 1/3 — Claude (proposer)    ✔
🔍 Round 2/3 — Codex (critic)      ✔
💡 Round 3/3 — Claude (proposer)    ✔
📝 Generating final synthesis...    ✔

════════════════════════════════════════════════════════════
[Final synthesized answer here]
════════════════════════════════════════════════════════════

Roles

| Role | LLM | Behavior | |------|-----|----------| | Proposer | Claude | Creative, constructive — generates ideas and integrates feedback | | Critic | Codex | Demanding but fair — finds flaws, suggests alternatives | | Synthesizer | Claude | Balanced — consolidates the best of all rounds |

Transcripts

With -s, a markdown transcript is saved with the full conversation:

transcripts/council-2026-03-22-231500.md

On errors or interrupts (Ctrl+C), a partial transcript is always saved so no work is lost.

License

MIT