Use plugins / Build plugins
Install a package for the agents you use, or create a portable Agent Plugins 1.0 package with instructions and tool configuration.
Use plugins
With Node.js 22 or newer:
npx universal-agent-plugins add context7The CLI asks which compatible agents to use and reports any remaining activation steps. To inspect and preview first:
npx universal-agent-plugins info context7
npx universal-agent-plugins add context7 --target codex,cursor --dry-runThe native installation guide also provides macOS, Linux and Windows executables. The native manager needs no Node.js, although individual plugins may require their own runtimes. Check npx universal-agent-plugins version when using npm: a package-manager channel can still provide an older CLI. The automatic selection below requires 0.1.94; use the native installer for the verified release. The commit-pinned Git Project command below also works with 0.1.93; signed Directory short-name Project installs require the current stable CLI.
CLI retains explicit project scope and the automatic install selection introduced in 0.1.94. It also adds a local management API and Pi extensions, Skills and MCP. To preview adding a package to a project:
For an eligible reviewed catalog entry, the published CLI accepts its signed Directory short name with explicit Project scope when the client supports all required components (for example, agentplugins add context7 --target codex --scope project --dry-run). Alternatively, use the reviewed exact commit-pinned Git source and compatible target. Replace OWNER/REPOSITORY, FULL_COMMIT_SHA, and PACKAGE_PATH; omit //PACKAGE_PATH for a repository-root package.
Template: github:OWNER/REPOSITORY@FULL_COMMIT_SHA//PACKAGE_PATH. The command below uses a real historical GitLab commit, not a currently reviewed catalog revision. For a new installation, copy the current reviewed source from the catalog.
npx universal-agent-plugins add github:777genius/universal-agent-plugins@2ddbb99dd190c1792b79904f9875e6322bccd243//plugins/gitlab --target codex --scope project \
--project-root /path/to/project --dry-runChoose an existing project directory. Add and maintenance commands default to user scope, so select project scope explicitly. In 0.1.94, install without a source argument selects the project only if the exact current folder contains a regular uap.toml; explicit scope wins and parents are not searched. Review the plan before omitting --dry-run. Native discovery, trust, authentication and successful MCP calls remain separate from writing the package's files.
Complete installation journey · Client compatibility and test boundaries
Restore a saved dependency set
Check what your selected user environment records:
npx universal-agent-plugins deps statusFor a saved uap.toml/uap.lock pair, export from an exchange folder:
npx universal-agent-plugins deps exportCopy the folder to another machine, install its target clients, and run there:
npx universal-agent-plugins deps import
npx universal-agent-plugins install --locked --scope userOnly the validated agreement and lock are transferred. Profiles, settings, credentials, receipts and plugin data stay separate. Installation still needs the exact sources or verified cached packages. For a project, commit the pair and restore with explicit install --locked --scope project. See maintenance and restoration for recovery and transfer details.
Build plugins
A standard package starts with root plugin.json, and can include skills/<name>/SKILL.md, mcp.json, or both. You can write these files manually and validate the package with the released installer:
npx universal-agent-plugins validate ./my-plugin
npx universal-agent-plugins add ./my-plugin --target codex --dry-runThese examples assume ./my-plugin already contains a complete package. The Build guide walks through a small manual Skill package and the source-build scaffolding tools.
Authoring availability: the current npm and native installer release does not include agentplugins author. Current source implements scaffolding, static checks, explicit MCP runtime tests, development cycles, dependency bootstrap and JSON maintenance. Use the source-build setup for those commands. Older authoring release evidence remains tied to its own version; it is not a promise about the current installer download.
Static validation does not establish runtime, OAuth or activation. MCP transport support also varies by client; for example, Codex does not support declared MCP SSE. Keep the package's requirements and remaining checks visible in its README.