brew install 777genius/agentplugins/agentplugins
agentplugins add context7

curl -fsSL https://raw.githubusercontent.com/777genius/universal-agent-plugins/main/install.sh | sh -s -- add context7

curl -fsSL https://raw.githubusercontent.com/777genius/universal-agent-plugins/main/install.sh | sh -s -- add context7

irm https://raw.githubusercontent.com/777genius/universal-agent-plugins/main/install.ps1 | iex
& "$HOME\.local\bin\agentplugins.exe" add context7

To install the latest installer globally with Node.js 22+:

npm install -g universal-agent-plugins

Homebrew and the installers select the native binary for your OS and architecture. The installer scripts verify its published SHA-256 and reported version, then replace the CLI atomically. They install into $HOME/.local/bin unless AGENTPLUGINS_BIN_DIR is set.

The native CLI does not require Node.js. The npx option requires Node.js 22+ and downloads and runs the verified Go binary. Individual plugins may have their own runtime requirements, which the CLI checks before installation.

The plugin package is downloaded and verified once, then prepared for each selected agent.

The installed package is standard-first:

plugin.json
├── skills/       optional reusable instructions
├── mcp.json      optional MCP servers
└── hooks/        optional client-specific extension

Skills and MCP are portable components. Hooks and other client-specific extensions depend on the target client; they do not imply portable behavior.

You can also install a local package or a pinned GitHub package without adding it to the registry. Direct-install examples are collected near the end of this README.

Other manifest formats are ignored and cannot override plugin.json.

npx universal-agent-plugins add context7 --target chatgpt,kiro

• ChatGPT: the CLI guides you to create a Developer Mode app for https://mcp.context7.com/mcp with No authentication, accepts the resulting asdk_app_... ID, and prepares a personal marketplace package. You still install that package and select Context7 in a new chat. When other clients are selected too, the CLI installs them first and reports ChatGPT as a separate setup step instead of cancelling the whole batch.
• Kiro: the CLI installs its owned skills and MCP entry while preserving unrelated configuration. On macOS and Windows it reports the remaining Kiro OAuth/restart step instead of claiming automatic runtime verification.

The same retained installation supports repeat add, update, repair, remove, and reinstall. ChatGPT availability still depends on an account or workspace where Developer Mode and custom apps are enabled.

See the real Context7 ChatGPT and Kiro E2E evidence.

A schema pass means that the package is well-formed; it does not prove runtime, OAuth, or activation in every client.

For Codex, declared MCP SSE is unsupported; stdio and Streamable HTTP retain their existing adapter support. Valid SSE components are excluded from Codex delivery without invalidating the package. See transport evidence and lifecycle behavior.

search combines the reviewed Registry Directory with a signed public Discovery Index containing conformant package paths. Discovery records are unreviewed metadata, not endorsements. They install only through a publisher-qualified exact-SHA selector and are validated again before mutation.

Before changing a client, the CLI validates the source and preflights every selected target. --dry-run prints the same plan without writing. Managed files and state are committed together; failures roll back what ownership proves safe or stop with a repair command. Preview does not activate a plugin or sign you in. Repair checks managed files; it does not prove external OAuth or runtime behavior.

# Install the only Agent Plugins package found at an exact commit
agentplugins add \
  owner/repository@0123456789abcdef0123456789abcdef01234567

# Choose a package explicitly when a repository contains several
agentplugins add \
  owner/repository@0123456789abcdef0123456789abcdef01234567//path/to/plugin

Remote installs require a full 40-character commit SHA. Branches, tags, and abbreviated SHAs are rejected. When no package path is given, the CLI uses a valid root plugin.json or auto-selects the only valid nested package that has mcp.json or skills/. If several packages match, it lists them and asks for an explicit //path. Repositories with more than 16 possible packages require an explicit path before candidate packages are fetched. The selected canonical path and package digest are stored for safe replay. Direct full-SHA installations remain immutable; use switch to move to another exact source. repair reapplies the recorded source, and remove changes only files owned by the CLI.

In qualified authoring builds, agentplugins author is the public authoring entrypoint. These examples require such a build or a current source build; installing the latest npm or native installer does not provide them.

Create and check a Skill package:

agentplugins author init ./my-plugin --template skill --name my-plugin
agentplugins author validate ./my-plugin
agentplugins author inspect ./my-plugin
agentplugins author test ./my-plugin

Current source builds also include JSON maintenance, dependency bootstrap, and a continuous MCP development loop. Plan mode is read-only, and --write is required for JSON maintenance changes:

agentplugins author normalize ./my-plugin --document plugin.json
agentplugins author normalize ./my-plugin --document mcp.json --write
agentplugins author import native ./claude.json --from claude \
  --output /absolute/path/to/new-plugin --name new-plugin \
  --description "Imported Claude MCP package" --write
agentplugins author dev ./my-plugin

Native import reads only the explicit strict-JSON file, skips unsafe or credential-bearing servers, and publishes only to an absent output. These commands become supported installation guidance after a signed agentplugins authoring release passes the public-channel checks.

Authoring validation and project doctor are distinct from installer agentplugins validate and agentplugins doctor. In qualified/source builds, MCP execution is available through author test and author dev. Dependency bootstrap is supported in qualified/source builds. Client projection, export/bundle, and publication are not exposed by the current authoring CLI. OAuth and activation inside a supported client still require client-specific verification. plugin.json is the only supported authoring manifest. JSON maintenance does not add a YAML reader, fallback, or migration workflow.