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.2

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.

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

start.js [profile] [--copy-profile]

Launches Chrome with remote debugging on port 9222.

./start.js                    # Use default profile
./start.js work              # Use named profile
./start.js work --copy-profile  # Copy Chrome profile for authenticated sessions

navigate.js [--new-tab]

Navigate to a URL.

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

evaluate.js "" | --file

Execute JavaScript in the current page context.

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

screenshot.js [output-path] [--full-page]

Capture screenshot of current page.

./screenshot.js
./screenshot.js output.png
./screenshot.js output.png --full-page

Usage with Claude Code

Add this directory to your session:

/add-dir ~/code/src/manzoid/browser-tools

Then Claude can use these tools by calling the scripts directly via Bash.

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