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

@llm-flow/multi-model

v0.1.0

Published

Run a prompt against multiple AI provider CLIs in parallel; ships as CLI and MCP server

Readme

@llm-flow/multi-model

Run a prompt against multiple AI provider CLIs in parallel and persist the results as a session.

Ships three surfaces backed by the same library core:

  • multi-model query — primary CLI subcommand
  • multi-model mcp — stdio MCP server exposing query, doctor, list-providers
  • multi-model doctor — checks provider CLIs are on PATH

Install

npm install -g @llm-flow/multi-model

Use

# Run a prompt against three providers in parallel
multi-model query \
  --providers claude,gemini,codex \
  --prompt-file ./review-prompt.md \
  --session-root .llm-flow/sessions

# Confirm providers are installed and authenticated
multi-model doctor

# Start the MCP server (stdio)
multi-model mcp

Output

Each query writes to <session-root>/<session-id>/:

prompt.txt           verbatim prompt sent to all providers
claude.md, claude.json
gemini.md, gemini.json
codex.md,  codex.json
metadata.json        session metadata (start/end times, durations, errors)

Library

import { fanOut, doctor } from '@llm-flow/multi-model';

const result = await fanOut({
  providers: ['claude', 'gemini'],
  prompt: 'Review this diff for security issues...',
  sessionRoot: '.llm-flow/sessions',
  profile: 'max-quality',
});

console.log(result.sessionDir);
console.log(result.results.map((r) => `${r.provider}: ${r.success ? 'ok' : r.error}`));

Provider CLIs assumed

| Provider | CLI | Max-quality model flag | |---|---|---| | claude | claude --print --output-format text | --model opus | | gemini | gemini | -m gemini-3.1-pro-preview | | codex | codex exec | -m gpt-5.4-codex |

If a provider CLI isn't on PATH, query reports it as failed and continues with the others. Run multi-model doctor to see what's missing.

License

MIT