GitHub announced on 2026-08-12 that Agent Plugins 1.0 support had shipped in VS Code, the Copilot CLI, the GitHub Copilot app and the Copilot SDK, available on all Copilot plans. The pitch is portability: build a plugin once and use it across compatible agent clients rather than rewriting the same extension for each tool. GitHub names AWS, Anysphere, Microsoft, OpenAI and Vercel as partners, and states that Google joined as a core maintainer on 2026-08-06.
The specification itself is deliberately narrow. Version 1.0.0 defines a directory layout plus a plugin.json manifest, and it recognizes exactly two component types: Agent Skills, placed in immediate child directories of a skills folder and required to conform to the Agent Skills specification, and Model Context Protocol servers, configured in an optional root mcp.json. It also standardizes placeholder expansion for runtime paths through PLUGIN_ROOT and PLUGIN_DATA variables, and sets minimum conformance requirements for clients that load and execute plugins. The published document carries Working Draft status, and governance is separated from the format itself through a Technical Charter, with a technical steering committee of core maintainers drawn from Amazon, Cursor, Microsoft, OpenAI and Vercel.
On the GitHub side, plugins are discoverable through the Awesome Copilot marketplace, existing GitHub Copilot plugins remain compatible, and enterprises can govern which plugins load through managed-settings.json.
This is the first credible attempt to standardize the layer above MCP. MCP settled how an agent talks to a tool; Agent Plugins settles how a bundle of skills and tool configurations is packaged, shipped and installed. For engineering leaders, the immediate consequence is that internal agent tooling built to this format stops being tied to one vendor’s client, and the vendor-neutral steering committee is what makes that claim more than marketing. The open question is coverage: the standard is only as portable as the set of clients that implement it, and the roster of maintainers, while broad, is not universal.