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

plugbook

v0.1.0

Published

Connect Plugbook (cited playbooks from videos, reels, posts and podcasts) to Claude Code, Codex, Gemini CLI, Cursor and VS Code, and use it from the command line.

Readme

plugbook

Connect Plugbook (teach your AI from the best creators: cited playbooks from YouTube videos, Instagram reels, LinkedIn posts and podcasts) to your AI tools, and use it from the command line.

Needs Node.js 18 or newer. No dependencies.

Connect your AI tools

npx plugbook connect            # asks before changing each tool
npx plugbook connect --dry-run  # shows what it would do

It finds the tools installed on your machine and adds the Plugbook MCP server:

| Tool | How | |---|---| | Claude Code | claude mcp add --transport http --scope user plugbook <url>, then /mcp in Claude Code to sign in | | Codex CLI | codex mcp add plugbook --url <url>, then codex mcp login plugbook | | Gemini CLI | gemini mcp add --transport http --scope user plugbook <url>, then /mcp auth plugbook | | Cursor | "plugbook": { "url": "<url>" } under mcpServers in ~/.cursor/mcp.json (a .bak copy is kept) | | VS Code | code --add-mcp '{"name":"plugbook","type":"http","url":"<url>"}', or servers.plugbook in the user mcp.json |

The URL comes from the server itself (/.well-known/oauth-protected-resource/mcp), so it follows Plugbook to its own domain. Each tool signs you in to Plugbook in the browser (Google or an email code); those calls use your Plugbook plan (the first month is free).

Command line

npx plugbook login                                   # browser sign-in, saves an API key
npx plugbook add https://www.youtube.com/watch?v=Iqy644uOOqM --pack Thumbnails --wait
npx plugbook status --pack Thumbnails
npx plugbook playbook Thumbnails > thumbnails.md
npx plugbook usage

The command line uses an API key, which is pay as you go ($1.00 per hour of video or podcast by the minute, $0.03 per post, $0.05 per playbook build, with free starting credit). The key is stored in ~/.config/plugbook/config.json (mode 600). PLUGBOOK_API_KEY and PLUGBOOK_URL override it. --json prints machine-readable output.

Made by Quarktex.