Install and manage Agent Plugins 1.0 across your AI agents with one CLI.

Quick start

Choose your operating system below. Already have Node.js 22+? You can use npx on any supported desktop OS without permanently installing the CLI.

macOS

With Homebrew:

brew install 777genius/agentplugins/agentplugins
agentplugins add context7

Without Homebrew, use the native installer:

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

Linux

Install the matching native binary and add your first plugin:

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

Homebrew also works on Linux: run brew install 777genius/agentplugins/agentplugins, then agentplugins add context7.

Windows

Run in PowerShell:

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

Any OS with Node.js 22+ (npx)

Run the command without permanently installing the CLI. npx downloads the verified Go binary and immediately runs the plugin command:

npx universal-agent-plugins add context7

Homebrew and the installers select the native binary for your OS and architecture. The 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.

Node.js is not a requirement of the native CLI. Individual plugins may declare their own runtime requirements; the CLI checks those separately before installation.

The CLI finds compatible agents installed on your computer and asks where to install the plugin. Choose one or several. The package is downloaded and verified once, then prepared for every agent you selected.

1. Run the command above.
2. Select the installed agents you want to use. If only one is found, it is selected automatically; if several are found, the CLI shows a multi-select.
3. Follow any activation or sign-in instruction printed by the CLI.
4. Start a new agent session and use the plugin.

Browse 2,500+ plugins

What the CLI does

• installs one plugin in one or several supported agents;
• updates, repairs, and removes only files it manages;
• converts the same Agent Plugins 1.0 package into each agent's native format;
• keeps activation and OAuth prompts visible to you.

Any Agent Plugins 1.0 package

The installed package is standard-first:

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

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.

plugin.yaml is the legacy plugin-kit-ai authoring format. It is not merged with or allowed to override plugin.json.

Supported clients

The CLI has adapters for:

Client	Delivery
Codex	managed package or OpenAI compatibility package
ChatGPT	registered app/binding where the package provides one
Cursor	native Agent Plugin and MCP/skills projection
GitHub Copilot CLI	native plugin and managed marketplace path
VS Code	prepared Copilot-compatible package
Kiro	native folder and Power import guidance
Claude Code	client-specific skills/MCP projection
Gemini CLI	client-specific configuration projection
OpenCode	client-specific configuration projection
Cline	client-specific configuration projection
Windsurf	client-specific configuration projection

Compatibility is package-specific. A schema pass means that the package is well-formed; it does not prove runtime, OAuth, or activation in every client. The CLI prints installed, prepared, activation required, and authentication pending as separate outcomes.

Find and verify plugins

search combines the reviewed Registry Directory with a signed public Discovery Index containing 2,500+ 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.

The registry is optional for direct installs, but it makes reviewed short names, provenance, compatibility notes, and safe discovery convenient:

Browse the registry · Submit a package

Lifecycle safety

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. OAuth and consent remain visible and controlled by you. No install telemetry is sent.

The CLI is an independent community project. It is not affiliated with OpenAI, Agent Plugins, or the vendors shown above.

More commands

For normal interactive use, omit --target and choose agents in the prompt. Use --target in scripts, CI, or whenever you want to name clients explicitly.

# Find and inspect plugins
agentplugins search docs
agentplugins info context7

# Install in specific agents
agentplugins add context7 --target codex,cursor,kiro

# Manage an installed plugin
agentplugins update context7 --target codex,cursor
agentplugins repair context7 --target codex,cursor
agentplugins remove context7 --target codex,cursor
agentplugins outdated --all
agentplugins update --all
agentplugins doctor

# Install a local Agent Plugins 1.0 package
agentplugins validate ./my-plugin
agentplugins add ./my-plugin

# 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.

Authoring and development

This repository also retains the original plugin-kit-ai authoring tools. Use the authoring guide at docs/PLUGIN_KIT_AI_AUTHORING.md when you want to build, validate, or export a package rather than install one.

Build one plugin and ship it to many AI agents. The repository includes starter templates for Codex and Claude across Go, Python, and Node/TypeScript.

Legacy authoring and SDK reference

plugin-kit-ai keeps authored source under plugin/, generates the supported outputs you need, and helps you validate the repo before handoff. This includes supported outputs for Claude, Codex, Gemini, Cursor, and OpenCode where the repo shape allows it. The honest promise is one repo / many supported outputs, not fake parity everywhere.

overview: plugin-kit-ai documentation fastest start: Quickstart choose by job first: Choose What You Are Building one repo, many outputs: What You Can Build honest caveat: Support Boundary

Choose What You Are Building

Connect an online service

Connect a local tool

Build custom plugin logic

Quick Start

brew install 777genius/homebrew-plugin-kit-ai/plugin-kit-ai
npm: `npm i -g plugin-kit-ai` or `npx plugin-kit-ai@latest ...`
pipx (`public-beta`, only when that release is published to PyPI): `pipx install plugin-kit-ai`
fallback installer: `curl -fsSL https://raw.githubusercontent.com/777genius/plugin-kit-ai/main/scripts/install.sh | sh`
plugin-kit-ai init my-plugin --template online-service
plugin-kit-ai init my-plugin --template local-tool
plugin-kit-ai init my-plugin --template custom-logic
plugin-kit-ai init my-plugin
plugin-kit-ai generate .
plugin-kit-ai validate . --platform codex-runtime --strict

Works Across Multiple Outputs

What To Do Next

Keep This Rule In Mind

Deep Product Details

Go Deeper By Goal

Fast Local Plugin

Production-Ready Plugin Repo

Already Have Native Config

examples/starters/README.md examples/local/README.md docs/CHOOSING_HELPER_DELIVERY_MODE.md the stable local Python and Node subset on codex-runtime and claude doctor, bootstrap, validate --strict, export, and bundle handoff for that stable local subset generate, import, and normalize are still public-beta docs/generated/target_support_matrix.md docs/generated/support_matrix.md docs/SUPPORT.md

SDK And CLI

Go SDK packages: github.com/777genius/plugin-kit-ai/sdk/claude, github.com/777genius/plugin-kit-ai/sdk/codex, and github.com/777genius/plugin-kit-ai/sdk/gemini.

./bin/plugin-kit-ai doctor ./my-plugin
./bin/plugin-kit-ai bootstrap ./my-plugin
./bin/plugin-kit-ai import ./native-plugin --from codex-runtime
./bin/plugin-kit-ai capabilities --format json

plugin-kit-ai validate --format json now emits the versioned plugin-kit-ai/validate-report contract. docs/CODEX_TARGET_BOUNDARY.md docs/VALIDATE_JSON_CONTRACT.md

go test ./...
make vet

• Contributing: CONTRIBUTING.md
• Security policy: SECURITY.md
• Support boundary: docs/SUPPORT.md
• Native CLI installation: docs/NATIVE_INSTALL.md
• Client E2E evidence: docs/AGENTPLUGINS_CLIENT_E2E.md
• Registry: https://github.com/777genius/universal-agent-plugins-registry

License

Universal Agent Plugins is licensed under the Apache License 2.0. Third-party components retain their original licenses; see NOTICE for attribution.