OpenAI, Amazon, Microsoft, Vercel Ship Agent Plugins 1.0
TL;DR
- Vercel originated the Agent Plugins proposal; the OpenAI-led headline obscures that the format came from a co-launcher with a smaller user base.
- The spec covers Skills and MCP server packaging only; marketplace, permissions, and discovery are explicitly out of scope, left to each client.
- Google shipped two concrete implementations on launch day, Agents CLI and Data Agent Kit, rather than a simple endorsement.
The interesting thing about Agent Plugins 1.0.0, published today by five companies that had every reason not to standardize, is that they standardized anyway. 9to5Mac framed the launch alongside GPT-5's one-year anniversary, and the pitch from OpenAI is deliberately modest: an open, vendor-neutral format that bundles Agent Skills and MCP servers into a portable directory with a small plugin.json file at its root.
The Technical Steering Committee is Amazon, Cursor, Microsoft, OpenAI and Vercel, with Google joining as a Core Maintainer represented by Kevin Hou, per the Google Developers Blog. Vercel initiated the proposal, according to Vercel's own writeup, and the launch client list covers ChatGPT and Codex, Cursor, GitHub Copilot, Kiro, and VS Code. Google says it has already wired support into its Agents CLI and Data Agent Kit.
The stakes here are less about the file layout and more about who controls distribution of the third-party layer that sits on top of agents. Until now, if you wrote a useful Skill you had to pick a client and repackage it for every other one, which quietly favored whichever platform had the largest install base. A shared portable directory shifts that leverage back toward the author, and toward whichever client is best at running the plugin rather than best at capturing the developer.
Several things the writeups leave unaddressed will shape whether this holds. Anthropic is not named as a maintainer or a supporting client, which for a launch this broad is a conspicuous silence. The spec is 1.0.0 rather than battle-tested, and none of the writeups explain how governance disputes get resolved once the interests of OpenAI, Google and AWS start to diverge on what the format should grow into. Client-specific namespaced folders exist in the layout, and they will be worth watching as a portability escape hatch.
If it holds, the winners are the skill authors and the smaller clients. This lands on top of more than 400 agent stories we have logged in the last 90 days, most of them describing yet another vendor-specific stack. Anyone who has been sitting on an agent integration idea because they did not want to maintain five parallel packagings of it just watched a lot of that friction disappear.
What others are reporting
-
Google Developers Blog Read →
Google adopted the format day one in two shipping products (Agents CLI and Data Agent Kit) and frames the spec within a broader ARD/AI Catalog discovery stack it controls.
Packaging is one job. Discovering and getting a plugin to a user is a different job, and it's worth being precise about which layer does what.
-
Vercel Read →
Vercel, as the proposal's originator, explains the spec's deliberate constraint: commands, hooks, and agent types are excluded until broader ecosystem convergence occurs.
Agent Plugins gives those shared components one predictable, structured home.
-
Agentic AI Foundation (AAIF) Read →
Independent governance body post emphasizes the five-vendor TSC structure and the narrow composable scope: packaging only, with discovery and trust left to clients.
Useful capabilities should be able to travel across agents. Agent Plugins unlocks interoperability across the agent ecosystem.
-
The Next Web Read →
Reports Vercel initiated the proposal rather than OpenAI, and surfaces developer skepticism alongside analysis of how standardization could entrench platform incumbents.
Build a plugin once and use it across compatible agent clients.
Originally reported by 9to5mac.com
Read the original article →Original headline: OpenAI, Amazon, Microsoft, Cursor and Vercel Launch Agent Plugins, a Shared MCP+Skills Package Format