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

promptheus

v2.1.1

Published

Interactive installer for the Promptheus toolkit — pick rules, agents & commands, get one wired-up AGENTS.md — npx promptheus init

Readme

promptheus

Interactive installer for the Promptheus toolkit — one command, three pickers, a repo your AI agent actually knows how to work in.

npx promptheus init

It scans your repo, detects your stack and your agent tool, then walks you through three full-catalog multi-select screens (everything relevant is pre-checked — untick what you don't want):

  1. Rules — 50+ production-grade rule sets (Next.js, Django, Go, Rust, Docker, TDD, Security…). Every rule you check is merged into one AGENTS.md — the open standard read by Claude Code, Codex, Cursor, Gemini and 30+ agents. In a monorepo each app gets its own AGENTS.md with its stack rules, plus a root file with the shared conventions and an app index.
  2. Subagents — a specialist crew (code reviewer, debugger, security auditor…) installed to .claude/agents/ (Claude Code only).
  3. Slash commands/review, /commit, /test, /debug… installed in your tool's native format and directory.

Then it wires the toolkit together: an ## Installed AI toolkit section is appended to your root AGENTS.md listing every installed subagent and slash command with its trigger, so your agent delegates and uses them proactively — without being asked.

Options

| Flag | Description | | ---- | ----------- | | -y, --yes | Accept the detected defaults (skip the pickers) | | --all | Select the entire catalogs (skips the pickers too) | | -f, --force | Overwrite files that already exist | | --dry-run | Show the full plan — files, merge composition, wiring — without writing | | --tool <t> | Target claude | cursor | gemini | codex | windsurf | | --dir <path> | Run against another directory | | -v, --version | Print the version |

--cursor, --gemini, --codex and --windsurf are shorthands for --tool.

Non-interactive usage

npx promptheus init --yes          # the detected default kit, no questions
npx promptheus init --all --force  # everything, overwriting existing files
npx promptheus init --dry-run      # print the plan, write nothing
npx promptheus list                # print the grouped catalogs
npx promptheus list rules          # …or just one of rules | agents | commands

Without a TTY (CI, scripts), init behaves like --yes.

Where things go

  • AGENTS.md — the merged rules + the toolkit wiring section (always, whatever the tool — it's the open standard)
  • .claude/agents/*.md — subagents (Claude Code)
  • .claude/commands/, .cursor/commands/, .gemini/commands/ (TOML), .codex/prompts/, .windsurf/workflows/ — slash commands per tool
  • README.md — an optional agent-ready badge (one line, idempotent)

Already-existing files are never touched unless you pass --force.

Env overrides

Everything is fetched live from the Promptheus sites; point the CLI elsewhere (mirror, staging, local dev) with:

| Variable | Default | | -------- | ------- | | PROMPTHEUS_RULES_URL | https://rules.promptheus.dev | | PROMPTHEUS_AGENTS_URL | https://agents.promptheus.dev | | PROMPTHEUS_COMMANDS_URL | https://commands.promptheus.dev | | PROMPTHEUS_HUB_URL | https://promptheus.dev |

If the rules index is unreachable, the CLI falls back to an embedded snapshot of the catalog so init keeps working.

Zero dependencies, copy-paste, public domain (CC0). Nothing is uploaded. Part of promptheus.dev.