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

promptpit

v0.1.4

Published

Portable AI agent stacks — collect, install, and share across Claude Code, Cursor, and more

Downloads

442

Readme

promptpit

Portable AI agent stacks. Collect, install, and share across Claude Code, Cursor, and more.

The Problem

Every AI coding tool has its own config format. Real-world stacks like gstack require manual git clone, editing CLAUDE.md by hand, and running setup scripts — and only work in one tool. There's no npm install for AI agent configurations.

The Solution

# Install someone's AI stack in one command
npx promptpit install github:garrytan/gstack

pit bundles skills, agent instructions, MCP server configs, and environment variables into a portable .promptpit/ stack that works across AI tools.

Install

npm install -g promptpit

Or use directly with npx promptpit <command>.

Commands

pit collect

Scans your project's AI tool configs and bundles them into a .promptpit/ stack.

pit collect                    # collect from current directory
pit collect ./my-project       # collect from specific directory
pit collect --output ./bundle  # custom output path (default: .promptpit)
pit collect --dry-run          # show what secrets would be stripped

Output:

.promptpit/
├── stack.json          # Manifest (name, version, skills, compatibility)
├── agent.promptpit.md  # Agent instructions (from CLAUDE.md, .cursorrules)
├── skills/             # SKILL.md files
├── mcp.json            # MCP server configs (secrets auto-stripped)
└── .env.example        # Required environment variables

pit install

Installs a stack into your project for all detected AI tools.

pit install                              # from .promptpit/ in current dir
pit install .promptpit                    # from local bundle
pit install github:user/repo             # from GitHub (auto-collects if no .promptpit/)
pit install github:user/[email protected]        # specific tag/branch
pit install github:user/repo --global    # install to ~/.claude/, ~/.cursor/ (all projects)
pit install --dry-run                    # preview without writing

Team setup

Commit .promptpit/ to your repo. Teammates install with:

pit install

Everyone gets the same AI config in their tool's native format. Like .editorconfig, but for AI coding tools.

Tip: Add .promptpit/ to your AI tool's ignore list so it doesn't scan the raw bundle files (they're already installed in the tool's native format). For Claude Code, add .promptpit to ignorePatterns in .claude/settings.json. For Cursor, add it to .cursorignore.

Supported Tools

| Tool | Read | Write | Format | |------|------|-------|--------| | Claude Code | CLAUDE.md, .claude/skills/, .claude/settings.json | Native SKILL.md | skill.md | | Cursor | .cursorrules, .cursor/rules/, .cursor/mcp.json | Auto-converted .mdc | mdc |

Adding a new tool requires one file + one registry entry. See src/adapters/ for examples.

How It Works

Collect: Detects which AI tools are configured in your project, reads their configs, merges them into a unified stack, strips secrets from MCP configs, and writes a .promptpit/ bundle.

Install: Reads a stack bundle, detects which AI tools are present in the target project, and writes config in each tool's native format. SKILL.md files are auto-converted to .mdc for Cursor. Content is wrapped in idempotent markers so multiple stacks coexist and re-installs replace cleanly.

Security

  • Secret stripping: MCP config values matching known patterns (API keys, connection strings, tokens) are replaced with ${PLACEHOLDER} during collect. .env.example is auto-generated.
  • Safe YAML parsing: All frontmatter is parsed with js-yaml JSON_SCHEMA to prevent !!js/function code execution from untrusted sources.
  • Env name validation: Dangerous env var names (PATH, NODE_OPTIONS, LD_PRELOAD) are blocked during install to prevent injection.
  • MCP trust warnings: Installing MCP servers shows a warning since they run as executables.
  • Input sanitization: GitHub owner/repo/ref are validated against a strict character allowlist.

Development

git clone <repo-url>
cd promptpit
npm install
npm test          # 71 tests, vitest
npm run build     # builds dist/cli.js via tsup
npm run lint      # TypeScript strict mode check

License

MIT