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

@agenthand/obo

v0.2.4

Published

Control your real Chrome browser via CLI. Let AI agents use your logged-in sessions, cookies, and extensions.

Readme

@agenthand/obo

Control your real Chrome browser via CLI. Let AI agents use your logged-in sessions, cookies, and extensions.

Unlike headless browsers, OBO operates your actual Chrome with all your logins intact.

Quick Start

# Start the server
npx @agenthand/obo

# In another terminal
obo tabs                    # List open tabs
obo snapshot <tabId> -i     # Get interactive elements
obo click <tabId> @e1       # Click an element
obo type <tabId> @e2 "hi"   # Type into a field
obo extract <tabId> --format md  # Extract page content as markdown

Requirements

Commands

| Command | Description | |---------|-------------| | obo status | Check connection status | | obo tabs | List open tabs | | obo new [url] | Open a new tab | | obo close <tabId> | Close a tab | | obo attach <tabId> | Activate a tab | | obo snapshot <tabId> [-i] | Get accessibility tree (-i: interactive only) | | obo screenshot <tabId> [-o file] | Take a screenshot | | obo open <tabId> <url> | Navigate to URL | | obo click <tabId> <ref\|x> [y] | Click element or coordinates | | obo type <tabId> <ref> "text" | Type into an element | | obo scroll <tabId> [--dy N] | Scroll the page | | obo wait <tabId> [--load\|--idle] | Wait for load/network idle | | obo extract <tabId> [--format json\|md] | Extract normalized page content | | obo eval <tabId> "expr" | Evaluate JavaScript |

Recommended Workflow

obo tabs
obo snapshot <tabId> -i
# interact: click/type/scroll
obo snapshot <tabId> -i

Element refs (@e1, @e2, ...) are snapshot-scoped. Re-snapshot after interactions or navigation.
Each snapshot includes snapshotId for traceability.

Error Handling

Most failures return:

{ "error": "...", "code": "..." }

Handle by code:

  • EXTENSION_NOT_CONNECTED: ensure extension/server are running, then retry.
  • TAB_ID_REQUIRED / TAB_NOT_FOUND: refresh tab list and retry with valid tabId.
  • TARGET_REQUIRED: take a fresh snapshot and use a new @e*.
  • REQUEST_TIMEOUT: retry with a narrower step.
  • INTERNAL_ERROR: stop and inspect route/payload.

Full table: docs/ERROR_CODES.md in the repository.

Claude Code Skill

npx skills add agenthand/obo

License

MIT