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

@openagere/plugins

v0.0.1

Published

Curated OpenAgere plugin marketplace bundle.

Readme

OpenAgere Plugins

This repository contains the curated OpenAgere plugin marketplace. It can be consumed directly from GitHub or from the npm package @openagere/plugins when GitHub access is slow or unavailable.

Each plugin lives under plugins/<name>/ and is listed in .agents/plugins/marketplace.json with a local source path. Plugin manifests may use the current Agere path .agere-plugin/plugin.json or compatible legacy paths such as .codex-plugin/plugin.json.

Distribution

  • GitHub source: https://github.com/openagere/plugins.git
  • npm package: @openagere/plugins
  • Release archive: GitHub Releases attach openagere-plugins-v<version>.zip

The npm package publishes the complete marketplace bundle:

.agents/plugins/marketplace.json
plugins/<plugin-name>/...
README.md
package.json

Local validation

Use Node.js 20 or newer.

npm run validate
npm pack --dry-run
npm run pack:zip

npm run validate checks that every marketplace entry:

  • uses a unique plugin name
  • points to a safe ./plugins/... local source
  • has a readable plugin manifest
  • matches the manifest name
  • declares valid installation and authentication policies

Release process

  1. Update package.json with the next version.

  2. Run npm run validate.

  3. Commit the version and marketplace changes.

  4. Create and push a matching tag:

    git tag v0.1.0
    git push origin main --tags
  5. The release workflow validates the marketplace, builds the zip archive, creates a GitHub Release, and publishes @openagere/plugins to npm.

The GitHub Actions release job requires the repository secret NPM_TOKEN with permission to publish @openagere/plugins.

Manual npm dry run

Before publishing a new version, preview the npm package contents:

npm pack --dry-run

To publish manually instead of using GitHub Actions:

npm publish --access public

Using npm as a fallback source

Agere can treat this npm package as a marketplace mirror. A client can download the package tarball, extract it to a local marketplace cache, and then install plugins from the extracted .agents/plugins/marketplace.json using the existing local-source plugin flow.

Recommended client fallback order:

  1. Sync https://github.com/openagere/plugins.git with Git.
  2. Download a GitHub Release archive.
  3. Download the npm tarball for @openagere/plugins from the configured registry.
  4. Extract the bundle and install plugins from the local marketplace file.