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

webresearcher

v1.0.0

Published

CLI tool that uses GPT-5.2 with web search for up-to-date research queries

Downloads

11

Readme

webresearcher

A CLI tool that uses GPT-5.2 with web search for up-to-date research queries.

Why?

Claude code's built-in web search is great for quick fact-lookups, but bad at detailed research.

Evaluated against Claude's built-in WebSearch tool across 14 query types. webresearcher won 13/14 on quality while remaining cost-effective (~$0.03/query).

Installation

Set your OpenAI API key in your path:

export OPENAI_API_KEY="your-key-here"

Requires Bun runtime.

# Clone the repo
git clone https://github.com/sky-xo/webresearcher.git
cd webresearcher

# Install dependencies
bun install

# Link globally
bun link

Usage

# Basic query (uses --effort low by default)
webresearcher "how do I stream responses with Vercel AI SDK?"

# Complex troubleshooting (use medium effort)
webresearcher --effort medium "why might Next.js build fail with module not found for an installed package?"

# See token usage and cost
webresearcher --verbose "current Bitcoin price"

Effort Levels

| Effort | Avg Latency | Avg Cost | Best For | |--------|-------------|----------|----------| | low (default) | ~17s | ~$0.03 | Most queries | | medium | ~29s | ~$0.04 | Complex troubleshooting | | high | ~60s+ | ~$0.08+ | Critical decisions |

Claude Code Integration

This tool was built to be used as a Claude Code skill. Install the skill:

webresearcher --install-skill

This copies the skill definition to ~/.claude/skills/webresearcher/SKILL.md. Claude will then know when to use webresearcher vs the built-in WebSearch tool.

Quick trigger: Tell Claude to "use wr" and it will use this tool.

When to Use What

| Query Type | Recommended Tool | |------------|------------------| | Simple factual ("latest version of X") | WebSearch | | Comparisons | webresearcher | | How-it-works explanations | webresearcher | | Best practices | webresearcher | | Troubleshooting | webresearcher --effort medium | | Documentation/code examples | webresearcher |

Flags

| Flag | Description | |------|-------------| | --effort low\|medium\|high | Reasoning effort (default: low) | | --verbose | Show token usage and cost | | --install-skill | Install Claude Code skill |

License

MIT