Agent Plugins 1.0.0 Releases Open Specification for Portable Agent Components

Agent Plugins, a new open specification for packaging reusable components that extend AI agents, has reached version 1.0.0. The initial Technical Steering Committee draws its core maintainers from Amazon, Cursor, Microsoft, OpenAI, and Vercel. The specification defines a shared directory format for two kinds of components: Agent Skills and MCP servers.

The problem it addresses is fragmentation. AI agent clients have developed their own plugin formats, even for identical underlying components. A plugin packaged for one client may need to be rearranged or duplicated for another. Agent Plugins attempts to lower that cost by describing a common layout for the parts of a plugin that can be portable.

An Agent Plugin is a directory containing a required plugin.json manifest and optional components in fixed places. plugin.json identifies the plugin and the version of the Agent Plugins spec it targets. A skills/ directory holds Agent Skills, using the format defined by the Agent Skills specification. An mcp.json file describes MCP servers, supporting stdio, Streamable HTTP, and legacy HTTP+SSE transports. Client-specific behavior can be dropped into reverse-domain extension namespaces such as com.example.client/hooks, so individual clients can extend a plugin without touching its portable core.

The scope is limited by design. Agent Plugins positions itself as an interoperability floor, not a complete standard for how plugins are distributed, installed, authenticated, or rendered to users. Those responsibilities remain with individual clients. The design accounts for clients with different needs and existing systems; the goal is a shared slot for the common parts, not a takeover of the whole plugin experience.

The governance process is also public. Proposals for new features and material changes start in GitHub Discussions, and must show a concrete portability need plus implementer support before progressing. The specification, schemas, and contribution process live in the Agent Plugins specification repository.

Whether the format will be adopted by enough clients to become useful remains open. A standard that nobody implements is just a directory structure. The presence of maintainers from five large agent vendors on the steering committee is a starting point, but the practical test will be in the plugins that ship and the proposals that gain implementers through the open process. The interoperability floor is defined; actual adoption is the next question.