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

@cluesmith/multisage

v1.0.4

Published

CLI client for Multisage — ask questions from your terminal

Readme

@cluesmith/multisage

Query Multisage from your terminal. Get answers from a panel of AI experts (Claude, GPT, Gemini) with a single command.

Installation

npm install -g @cluesmith/multisage

Or use without installing:

npx @cluesmith/multisage "What's the best programming language for beginners?"

Setup

  1. Create an API key at multisage.ai/settings
  2. Set the environment variable:
export MULTISAGE_API_KEY=msk_your_key_here

Usage

# Ask a question
multisage "React vs Vue for a new project?"

# Get full expert details and stages
multisage --full "Should I use TypeScript?"

# Output as JSON (for scripting)
multisage --json "Best laptop for developers?"

# Full details as JSON
multisage --json --full "React vs Vue?"

# Pipe to a markdown renderer
multisage "Explain async/await" | glow

# Save to file
multisage "Best practices for REST APIs" > advice.md

# Use with a different server
multisage --api-url https://staging.multisage.ai "test question"

Options

| Flag | Short | Description | Default | |------|-------|-------------|---------| | --api-key <key> | -k | API key (overrides env var) | $MULTISAGE_API_KEY | | --api-url <url> | -u | Base URL for API | https://multisage.ai | | --full | -f | Include expert details and all stages | false | | --json | -j | Output as structured JSON | false | | --quiet | -q | Suppress progress spinner | false | | --version | | Show version | | | --help | | Show help | |

Output Modes

Default (Markdown)

Prints the synthesized answer as markdown to stdout.

Full (--full)

Prints all stages: Quick Answer, Expert Responses (per expert), Synthesis, and Debate (if triggered).

JSON (--json)

Outputs the API response as JSON to stdout. Combine with --full for the complete response schema.

Error Codes

| Error | Message | |-------|---------| | Invalid API key | "Invalid API key. Check your key at: https://multisage.ai/settings" | | Insufficient credits | "Insufficient credits. Purchase more at: https://multisage.ai/settings" | | Rate limited | "Rate limit exceeded. Try again in N seconds." | | Concurrent limit | "Too many concurrent requests. Try again in a few seconds." | | Network error | "Could not connect to {url}." | | Timeout | "Request timed out after 300 seconds." |

All errors exit with code 1. With --json, errors are also output as JSON to stdout for programmatic handling.

Requirements