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

pi-package-test

v0.1.6

Published

Test package for pi coding agent with extensions, skills, themes, and prompts

Readme

pi-package-test

A reference package demonstrating pi coding agent's package system features.

What This Demonstrates

1. Package Structure

A pi package can include multiple resource types:

pi-package-test/
├── extensions/          # *.ts or *.js files
├── skills/              # Directories with SKILL.md
├── themes/              # *.json files
├── prompts/             # *.md files
├── node_modules/        # Bundled dependencies (optional)
└── package.json

If you follow this convention, no pi field is needed in package.json. Pi auto-discovers resources from these directories.

The pi field is only needed when:

  • Resources are in non-standard locations
  • You want to include resources from bundled dependencies
  • You want to exclude certain files via patterns

2. Pi Manifest with Glob Patterns

The pi field in package.json declares resources using glob patterns and exclusions:

{
  "pi": {
    "extensions": [
      "extensions",
      "node_modules/shitty-extensions/extensions",
      "!**/cost-tracker.ts",
      "!**/loop.ts"
    ],
    "skills": [
      "skills",
      "node_modules/shitty-extensions/skills"
    ],
    "themes": ["themes"],
    "prompts": ["prompts"]
  }
}

3. Bundling Other Pi Packages

To include resources from another package, use bundledDependencies to embed it in the published tarball:

{
  "dependencies": {
    "shitty-extensions": "^1.0.1"
  },
  "bundledDependencies": [
    "shitty-extensions"
  ]
}

Without bundledDependencies, npm's hoisting could move the dependency elsewhere, breaking the node_modules/... paths in the manifest.

4. User-Side Filtering

Users can narrow down what the manifest provides in their settings.json:

{
  "packages": [
    {
      "source": "npm:pi-package-test",
      "extensions": ["!**/oracle.ts"],
      "skills": [],
      "themes": []
    }
  ]
}

User filters layer on top of manifest filtering:

  1. Manifest patterns are applied first (defines what package provides)
  2. User patterns are applied on top (narrows down further)

So if the manifest excludes 10 extensions and user adds "extensions": ["!**/oracle.ts"], all 11 are excluded.

Contents

Extensions

| Name | Source | Description | |------|--------|-------------| | confirm-destructive.ts | local | Prompts for confirmation before destructive bash commands | | custom-footer.ts | local | Adds custom status to the footer | | oracle.ts | bundled | Oracle extension for predictions | | memory-mode.ts | bundled | Memory mode for persistent context |

Skills

| Name | Source | Description | |------|--------|-------------| | transcribe | local | Speech-to-text transcription using Groq Whisper API | | a-nach-b | bundled | Austrian public transit routing |

Themes

  • funky - A vibrant neon color theme

Prompt Templates

  • /review - Review code for bugs and improvements
  • /explain - Explain code in simple terms

Installation

pi install npm:pi-package-test

License

MIT