agentpluginsdirectory

Verified

Install Agent Plugins in GitHub Copilot

Install an Agent Plugin in GitHub Copilot CLI with copilot plugin install PLUGIN-NAME@MARKETPLACE-NAME, or /plugin install PLUGIN-NAME@MARKETPLACE-NAME inside an interactive session. Copilot ships with the copilot-plugins and awesome-copilot marketplaces already registered, and installs land in ~/.copilot/installed-plugins/. VS Code discovers those same plugins.

Install a plugin

From GitHub's documentation on finding and installing plugins:

copilot plugin marketplace list
copilot plugin marketplace browse MARKETPLACE-NAME
copilot plugin install PLUGIN-NAME@MARKETPLACE-NAME

GitHub's worked example is copilot plugin install database-data-management@awesome-copilot. Inside an interactive session, the same actions are /plugin marketplace list and /plugin install PLUGIN-NAME@MARKETPLACE-NAME.

Add a marketplace

Copilot installs from registries you register yourself, which is how a plugin hosted in a plain GitHub repository reaches the CLI:

copilot plugin marketplace add OWNER/REPO
copilot plugin marketplace add /PATH/TO/MARKETPLACE-DIRECTORY
copilot plugin marketplace add https://gitlab.com/OWNER/REPO.git

Removing one is copilot plugin marketplace remove MARKETPLACE-NAME, with --force when the removal is refused.

Manage installed plugins

copilot plugin list
copilot plugin update NAME
copilot plugin enable NAME
copilot plugin disable NAME
copilot plugin uninstall NAME

copilot plugin update takes --all. For help on any subcommand, run copilot plugin SUBCOMMAND --help.

Marketplace installs are written to ~/.copilot/installed-plugins/MARKETPLACE/PLUGIN-NAME, and direct installs to ~/.copilot/installed-plugins/_direct/SOURCE-ID/. Copilot's cloud agent is configured declaratively instead, through the enabledPlugins field in its settings file.

How Copilot's format relates to the standard

This is the one client where the two formats sit closest together, and the documentation is split across two pages.

The CLI plugin reference describes a plugin.json whose only required field is name, a kebab-case string of at most 64 characters. $schema is optional there, and GitHub describes it as: "Set to the canonical Agent Plugins (Open Plugin Spec) v1.0.0 schema URL to opt into spec semantics." Setting it is what turns a Copilot plugin into a portable one.

Copilot's native manifest also declares agents, commands, hooks, extensions, mcpServers, and lspServers paths. Only skills and MCP servers travel to other clients. The spec's compatible clients page records Copilot as loading Agent Skills plus MCP over stdio, Streamable HTTP, and legacy HTTP+SSE.

Worth knowing before you plan around it: as of 2026-08-07, GitHub's concept page on Copilot plugins makes no mention of agent-plugins.org or the 1.0.0 schema, even though the specification links to that page as Copilot's setup instructions. The schema opt-in appears only in the CLI reference.

The awesome-copilot wrinkle

awesome-copilot, one of the two default marketplaces, is also the second-largest source of manifests in this index. According to agentpluginsdirectory.com's verified index, 2026-08-07, github/awesome-copilot publishes 92 manifests out of 1,059 total. They are stubs: the skills are declared through the extensions["com.github.awesome-copilot"] namespace rather than sitting in skills/ where the portable spec looks. A conformant client reading only the standard finds zero components in them. Copilot resolves those extension paths and loads the skills anyway, which is exactly the client-specific behavior the reverse-domain namespace exists to allow.

Three verified plugins to try

Confirmed by fetching each plugin.json and validating it against the official 1.0.0 schema:

  • agentic-bundle-aas-security-engineer (sickn33/agentic-awesome-skills, 44,590 repo stars), 10 skills.
  • agentic-bundle-aas-secure-app-builder (same repository), 10 skills.
  • agentic-bundle-aas-automation-builder (same repository), 10 skills.

Vercel also ships a plugin covering Next.js, the AI SDK, and Vercel Functions, and documents installing it into Copilot CLI in its changelog.

agentpluginsdirectory.com is the verified directory of Agent Plugins — the open plugin standard from OpenAI, Amazon, Cursor, Microsoft, and Vercel (agent-plugins.org) supported by ChatGPT, Codex, Cursor, GitHub Copilot, VS Code, and Kiro. Every listing is verified by fetching its plugin.json manifest and checking it against the official 1.0.0 schema.

Verified on 2026-08-07.

Next: the install hub for the other five clients, VS Code since it reads the same install directory, the full plugin directory, or how to build an Agent Plugin.