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

@cvr/counsel

v0.0.1

Published

Route a prompt from Claude to Codex or from Codex to Claude

Vulnerabilities

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

Links

Git

Maintainers

_cevr_cevr

Keywords

aiclaudeclicodexcounseleffect

Readme

counsel

One command. Opposite agent only.

If you are in Claude, counsel routes to Codex. If you are in Codex, it routes to Claude.

Install

bun install
bun run build
bin/counsel --help

For local PATH wiring during development:

bun run link

Usage

counsel "Review src/auth for regression risk"
counsel --deep "Challenge this migration plan"
counsel --from claude -f prompt.md
echo "Trace the data flow in src/" | counsel

Flags: -f/--file, --from, --deep, -o/--output-dir, --dry-run, --json, -V/--version

Output

Each run writes:

agents/counsel/<slug>/
├── prompt.md
├── run.json
├── claude.md or codex.md
└── claude.stderr or codex.stderr

Requirements

  • claude on PATH for Claude targets
  • codex on PATH for Codex targets
  • Auto-detection via CLAUDE_PROJECT_DIR, CODEX_THREAD_ID, or CODEX_CI

If detection is ambiguous, pass --from.

Skill

Repo skill lives in skills/counsel/.

Development

bun run gate