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

claude-setups

v0.9.0

Published

Publish, discover, and mirror Claude Code setups — safely, via GitHub

Readme


People are sharing Claude Code setups everywhere — Reddit posts, GitHub repos, blog articles — but there's no single place to browse, compare, and install them. claude-setups is that place: a community registry where you publish your hooks, CLAUDE.md, skills, commands, and agents, and anyone can mirror your entire setup with one command.

Quick Start

npx -y claude-setups publish          # share your setup
npx -y claude-setups mirror alice/setup   # clone someone else's
npx -y claude-setups browse           # explore the gallery

What Gets Shared

| Shared (you review each file) | Never shared (no code path exists) | |---|---| | Plugin & marketplace identifiers | settings.json | | MCP server names + commands | ~/.claude.json (OAuth tokens) | | Hook scripts (hooks/*.sh) | MCP env sections (API keys) | | CLAUDE.md and root *.md | Absolute filesystem paths | | Skills, commands, agents | |

Features

Publish

npx -y claude-setups publish

That's it. The CLI uses claude -p to analyze your setup and suggest title, description, tags, and specialties automatically. You review the suggestions, confirm or edit, and publish. No flags needed.

By default, publish includes your hooks, CLAUDE.md, skills, commands, and agents as a bundle — showing each file for interactive include/exclude with gitleaks regex scanning. Nothing uploads until you type publish. Use --no-bundle to publish only plugin/MCP identifiers.

Flags (--author, --slug, --title, etc.) are still supported for scripting and CI.

Mirror

Replicate someone else's setup on your machine. One command installs plugins, marketplaces, MCP servers, and extracts bundle files — all idempotently.

npx -y claude-setups mirror alice/demo-setup
  • Installs plugins at the exact version the publisher exported
  • Extracts hooks, skills, commands into ~/.claude/
  • Backs up existing files as .bak on conflict
  • Skips anything already installed (safe to re-run)
  • Sets chmod +x on hook scripts automatically

Browse

Explore published setups in the community gallery:

npx -y claude-setups browse

Or visit the gallery directly.

Revoke

Remove a previously published setup from the registry:

npx -y claude-setups revoke --author yourname --slug my-setup

How It Works

┌──────────────┐     publish      ┌──────────────────┐     GitHub Action     ┌─────────────┐
│  your        │  ──────────────► │  GitHub Issue     │  ─────────────────►  │  Registry    │
│  ~/.claude/  │   descriptor +   │  (setup:submission│    validate + move   │  (gallery +  │
│              │   bundle.tar.gz  │   label)          │                      │   JSON API)  │
└──────────────┘                  └──────────────────┘                      └──────┬───────┘
                                                                                   │
┌──────────────┐     mirror       ┌──────────────────┐                             │
│  their       │  ◄────────────── │  Descriptor JSON  │  ◄─────────────────────────┘
│  ~/.claude/  │   fetch + extract│  + bundle.tar.gz  │
└──────────────┘                  └──────────────────┘

The registry is a static GitHub Pages site — no server, no database, no accounts beyond GitHub. Publishing creates a GitHub Issue; a GitHub Action validates and ingests it. Mirroring fetches static JSON + tarball.

Relation to claude-snapshot

| | claude-snapshot | claude-setups | |---|---|---| | Purpose | Backup & sync across your own machines | Share with the community | | Audience | Private (your machines only) | Public (community gallery) | | Reads settings.json | Yes | No | | Use case | Multi-machine sync, disaster recovery | Discovery, showcase, one-command clone |

Both tools coexist. Use claude-snapshot for private backup; use claude-setups to share publicly.

Security

Sensitive files (settings.json, ~/.claude.json, MCP env sections) are excluded by design — no code path exists to read them. Content files go through interactive preview with gitleaks regex scanning before publish. Full details in docs/SECURITY_PREMISE.md.

Contributing

PRs welcome! See the registry repo for gallery/validation contributions.

License

MIT