Skip to content

openagere/plugins

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

229 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

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.

About

OpenAI Plugins

Resources

Stars

Watchers

Forks

Packages

 
 
 

Contributors

Languages

  • Python 67.8%
  • JavaScript 14.8%
  • Standard ML 6.2%
  • Shell 3.9%
  • HTML 3.2%
  • HCL 1.9%
  • Other 2.2%