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

@manzoid2/browser-tools

v1.0.3

Published

Minimal Puppeteer-based browser automation toolkit for AI coding agents

Readme

Browser Tools

Minimal Puppeteer-based browser automation toolkit for AI coding agents. Inspired by Mario Zechner's approach.

Installation

# Install globally
npm install -g @manzoid2/browser-tools

# Or use directly with npx
npx @manzoid2/browser-tools <command>

Quick Start

# Start browser
browser-start

# Navigate to a page
browser-navigate https://example.com

# Execute JavaScript
browser-evaluate "document.title"

# Take screenshot
browser-screenshot test.png

Philosophy

Instead of heavy MCP servers, these are simple bash-callable scripts that leverage the agent's existing JavaScript knowledge. Total documentation: ~225 tokens vs 13k+ for MCP equivalents.

Tools

browser-start [profile] [--copy-profile] [--size=WxH]

Launches Chrome with remote debugging on port 9222.

browser-start                           # Default profile, 1440x900 window
browser-start work                      # Named profile
browser-start work --copy-profile       # Copy Chrome profile for authenticated sessions
browser-start --size=1920x1080          # Custom window size
browser-start work --size=1280x720      # Named profile + custom size

browser-navigate [--new-tab]

Navigate to a URL.

browser-navigate https://example.com
browser-navigate https://example.com --new-tab

browser-evaluate "" | --file

Execute JavaScript in the current page context.

browser-evaluate "document.title"
browser-evaluate "document.querySelectorAll('a').length"
browser-evaluate --file script.js

browser-screenshot [output-path] [--full-page]

Capture screenshot of current page.

browser-screenshot
browser-screenshot output.png
browser-screenshot output.png --full-page

Usage with Claude Code

Once installed globally, Claude can use these tools directly via Bash without needing to add any directories.

Why This Over MCP?

  • Token efficient: Minimal docs, agent already knows JavaScript
  • Composable: Output goes to disk, can be chained
  • Extensible: Add new tools easily without versioning hell
  • Simple: Just Node.js scripts, no protocol layer