Agent Plugins 1.0 lands: one plugin format for Copilot, Cursor, Codex
GitHub flips it GA in VS Code, Copilot CLI and the app: a directory of skills plus MCP servers that ports between clients, backed by OpenAI, Google and AWS.
Copy markdown
Build the plugin once, run it everywhere
GitHub flipped Agent Plugins 1.0 to GA in VS Code, Copilot CLI, the Copilot SDK and the Copilot app, on every Copilot plan. The same plugin now loads unchanged across compatible agent clients, so you stop re-authoring the same MCP+skills bundle per tool.
A plugin is just a directory
The format is deliberately minimal: a plugin.json (only $schema and name required), a skills/ folder of SKILL.md files, and an mcp.json wiring up stdio or HTTP MCP servers. You can package the MCP servers and skills you already run into one portable folder this weekend.
It collapses six rival formats
The spec unifies plugin manifests that were fragmented across Cursor, Codex, Claude, Copilot and legacy OpenPlugin. Clients reading it at launch include VS Code, Cursor, GitHub Copilot, ChatGPT & Codex and Kiro; the standard is co-authored with AWS, Microsoft, OpenAI, Vercel and Google.
Installs from Awesome Copilot by default
GitHub ships an Awesome Copilot marketplace enabled out of the box in VS Code, Copilot CLI and the app; grab a plugin with `npx plugins add <org>/<name>` or `@agentPlugins <name>` in VS Code. Orgs on Business/Enterprise gate installs via managed-settings.json.
The gap: no provenance yet
Distribution is explicitly out of scope: the standard defines no registry, no signing and no dependency resolution, so third-party plugins install unverified. It also still carries a Working Draft status label despite the 1.0 name, so treat unknown plugins like unknown npm packages.