Agent Plugins: A Vendor-Neutral Push to Unify AI Agent Extensions

Six major AI tooling vendors just agreed on a single format for packaging agent extensions. The Agent Plugins standard, launched this month by Vercel, AWS, OpenAI, Microsoft, GitHub, and Cursor's parent Anysphere, defines a portable folder structure for agent skills and MCP servers that any compatible coding assistant can load. If you maintain a plugin or build internal tools for multiple agent platforms, this is the most practical standardization event in the agent ecosystem this year.

What the Agent Plugins Standard Packages

The standard specifies three things in a folder: a top-level plugin.json manifest, a skills/ directory containing reusable instructions for the agent, and an mcp.json file that describes tool connections. That's it for version 1.0. The group deliberately kept the scope narrow to avoid stalling on controversial features, according to AWS senior principal engineer Clare Liguori, who said skills and MCP servers were already broadly adopted and uncontested across different coding agents.

The compact format means a plugin built for OpenAI's Codex can also run in Cursor, GitHub Copilot, VS Code, or AWS Kiro, provided the developer follows the same folder layout. The vendors also built in a mechanism for proprietary extensions: any company can add new configuration under a folder named with its own domain, enabling features that aren't in the standard yet without breaking compatibility.

The Practical Win: One Plugin, Multiple Agents

The core problem the standard solves is duplication. As Vercel CTO Malte Ubl told The AI Economy, his team was building skills for themselves and realized "there is no good way to do that" without publishing ten different installation instructions. AWS saw the same pattern with enterprise customers who ran multiple coding clients and couldn't share a single skill or MCP server across them.

For builders, the win is straightforward: you write and maintain one plugin package instead of one per agent. The standard's design intentionally decouples "what the thing is" from "how it travels," Ubl said, so future agent capabilities can reuse the same distribution mechanism. This lowers the barrier for open-source maintainers and SaaS companies to support every major coding agent without dedicating an engineer per platform.

What's Missing and Who's Not At The Table

The first release leaves out several important features. Hooks and agent configuration are on the roadmap but need more discussion to separate universally useful hooks from vendor-specific ones. Auto-updating is also unresolved, as Ubl noted that plugins delivered through OpenAI and Anthropic marketplaces already get it, but writing that into the standard is difficult when each marketplace controls its own update pipeline.

Governance of the standard itself is still an open question. Neither a governance body nor a plan to donate the spec to an independent foundation has been announced, unlike other agent standards (Agent2Agent, AGNTCY) that were placed under the Linux Foundation. The steering committee is currently watching vendor extensions in hopes of promoting the most universal ones into a future version.

Anthropic's Claude is conspicuously absent from the launch group. Ubl confirmed that conversations with Anthropic took place but acknowledged "some interesting dynamics going on." Claude is one of the most popular coding agents and originated both MCP and agent skills, so its non-participation creates a practical gap. Plugins packaged under the standard will not run on Claude unless Anthropic decides to adopt the format later.

What Builders Should Do Now

If you maintain an agent skill or MCP server, you should evaluate repackaging it into the Agent Plugins format to reach the five supporting clients. The standard is simple enough that the migration is mostly renaming folders and adding a manifest. For enterprise teams running multiple coding agents internally, this format removes the need to maintain separate plugin distributions and could become your default packaging convention. The absence of Claude and unresolved governance are worth monitoring, but the consortium's combined market share means the standard has strong momentum out of the gate.