JSPM

@a5c-ai/agent-plugins-mux

5.0.1-staging.ff407b73
  • ESM via JSPM
  • ES Module Entrypoint
  • Export Map
  • Keywords
  • License
  • Repository URL
  • TypeScript Types
  • README
  • Created
  • Published
  • Downloads 2408
  • Score
    100M100P100Q107597F
  • License MIT

Cross-harness plugin compiler — compiles a single plugin.json manifest into 9 AI coding agent plugin formats

Package Exports

  • @a5c-ai/agent-plugins-mux
  • @a5c-ai/agent-plugins-mux/dist/index.js

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 (@a5c-ai/agent-plugins-mux) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

@a5c-ai/agent-plugins-mux

Cross-harness plugin compiler for converting a unified plugin.json source tree into harness-specific plugin packages.

Install

npm install @a5c-ai/agent-plugins-mux

CLI usage:

npx @a5c-ai/agent-plugins-mux agent-plugins-mux --help

This package ships the built compiler in dist/ and this package README for npm auditability.

CLI Surface

The current public CLI commands are:

  • compile --target <name|all> --output <dir> to emit target plugin surfaces
  • validate --source <dir> to validate a unified plugin directory without writing output
  • init --name <name> [--template <minimal|full|hooks-only>] [--output <dir>] to scaffold a valid unified plugin source tree
  • list-targets to print the supported target registry

The diff command is still reserved and currently exits with a not-implemented error. The supported targets are claude-code, codex, cursor, gemini, github-copilot, pi, oh-my-pi, opencode, and openclaw.

API Surface

import {
  compile,
  compileAll,
  validateDirectory,
  validateSchema,
} from "@a5c-ai/agent-plugins-mux";

The package exports the compiler pipeline and related types:

  • manifest schema and package types
  • directory validation, target resolution, transform, emit, and verify helpers
  • target registry accessors and compilation entrypoints

Validation

npm run build --workspace=@a5c-ai/agent-plugins-mux
npm run test --workspace=@a5c-ai/agent-plugins-mux
npm run verify:metadata
npm pack --json --dry-run --workspace=@a5c-ai/agent-plugins-mux

Release Expectations

@a5c-ai/agent-plugins-mux is published from the central release workflows. Keep this README aligned with the actual command set and compiler exports, and keep package.json#files limited to the built compiler plus package documentation.