Package Exports

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (@openagere/plugins) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

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

Update package.json with the next version.
Run npm run validate.
Commit the version and marketplace changes.

Create and push a matching tag:

git tag v0.1.0
git push origin main --tags

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:

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