777genius/universal-agent-plugins

Our installer automation principle is to complete every ownership-safe client step automatically and ask the user only for genuine external approvals, authentication, or reloads.
Read the documentation ·
Browse plugins
Use plugins
Install, inspect, update, repair, and remove packages with the existing installer.
The Use guide source collects this journey.
See Build plugins below to create and check a package.
Quick start
With Node.js 22+, run:
The CLI automatically finds compatible agents, including Codex and Claude Code.
Choose agents if several are found; a single detected agent is selected automatically.
Follow the printed setup steps, then start a new agent session.
Other installation options
macOS
With Homebrew:
Without Homebrew, use the native installer:
Linux
Install the matching native binary and add your first plugin:
Homebrew also works on Linux: run brew install 777genius/agentplugins/agentplugins,
then agentplugins add context7.
Windows
Run in PowerShell:
To install the latest installer globally with Node.js 22+:
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.
Browse 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
Install from the registry, a local folder, or a GitHub repository pinned to an
exact commit. plugin.json is the sole supported authoring manifest.
Package layout and portability
The installed package is standard-first:
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.
Supported clients
The CLI has adapters for:
| Client | Delivery |
| --- | --- |
| Codex | plugin package prepared for Codex |
| ChatGPT | app setup; Context7 includes guided personal setup (Developer Mode and custom apps required) |
| Cursor | native plugin with skills and MCP servers |
| GitHub Copilot CLI | native plugin installed through a managed marketplace |
| VS Code | plugin package prepared for Copilot |
| Kiro | skills and MCP setup; OAuth/restart may be required |
| Claude Code | native Claude Code plugin installation |
| Gemini CLI | skills and MCP configuration |
| OpenCode | skills and MCP configuration |
| Cline | skills and MCP configuration |
| Windsurf | MCP configured; skills prepared for manual use |
| Grok Build | native skills/MCP plugin; Grok CLI install and verification when available |
| Kimi Code | native skills/MCP plugin and managed user registry; reload required |
Grok Build and Kimi Code accept automatic user-scope installation of portable skills and stdio/HTTP MCP servers through agentplugins add ./my-plugin --target grok,kimi. The CLI verifies native registration and supports update and removal. A running client still needs a reload, and remote MCP authentication/connectivity is verified in that client. Agent, hook, command, and LSP components are outside these two adapters' current supported scope.