Agent Plugins: The New Portable Standard for AI Agent Extensions

AI agents are only as useful as the components you can plug into them. For the past year, that meant learning a different packaging format for every client: Claude Code plugins, Cursor extensions, VS Code agent skills, and a dozen other bespoke layouts — even when the underlying component was the same.

Agent Plugins (version 1.0.0) is a new, vendor-neutral standard that fixes this. Backed by a Technical Steering Committee with core maintainers from Amazon, Cursor, Microsoft, OpenAI, and Vercel, it defines one portable package format for the two most common agent extension types: Agent Skills and MCP servers.

The problem: one component, many wrappers

Before Agent Plugins, a "skill" that summarized documents lived in one folder layout for Claude Code, another for Cursor, and a third for a custom agent framework. Authors had to rearrange or duplicate the same component for every client. Distribution, permissions, and client-specific features stayed proprietary — but the content of a skill or MCP server was always portable.

Agent Plugins draws the line in the right place: it standardizes the parts that can be portable, and leaves everything else (distribution, install UX, permissions) under each client's control.

The portable package

An Agent Plugin is a directory with a required manifest and optional components in fixed locations:

my-plugin/
├── plugin.json          # required: identifies the plugin
├── skills/
│   └── summarize/
│       ├── SKILL.md
│       ├── scripts/
│       └── references/
├── mcp.json             # optional: stdio / Streamable HTTP / HTTP+SSE servers
└── com.example.client/  # optional: client extension namespaces

• plugin.json — the manifest. Only $schema and name are required; version, description, author, homepage, repository, license, and keywords are all optional metadata.
• skills/ — Agent Skills in the exact format defined by the Agent Skills specification.
• mcp.json — describes stdio, Streamable HTTP, or legacy HTTP+SSE MCP servers.
• Extension directories — reverse-domain namespaces (like com.example.client) let individual clients add behavior without forking the portable core.

Because both referenced standards are themselves open and stable, a plugin written once can be loaded by any conforming client — no reshuffling.

Ecosystem traction

The standard is young but adoption is real. On GitHub, more than a thousand repositories already reference the official agent-plugins.org/schemas schema in their plugin.json files. Notable examples include:

• awslabs/agent-plugins — AWS's official plugin pack, equipping agents with skills for architecting, deploying, and operating on AWS.
• github/awesome-copilot — a single monorepo shipping a dozen plugins for Copilot workflows.
• The agentplugins GitHub organization hosts the specification, the official site, and a canonical example plugin with a migration guide.

Development happens in the open: proposals and material changes start as GitHub Discussions in the spec repository, where they must demonstrate a concrete portability need and implementer support.

Where to find plugins

Because Agent Plugins is a packaging standard rather than a registry, discovery is fragmented — which is exactly the gap a directory fills. AIMCP now curates an Agent Plugins directory at /plugins: every entry is crawled from GitHub, validated against the official JSON schema, summarized in multiple languages by AI, and linked back to its source repository.

Browse the directory, filter by component type (skills, MCP servers), and find a plugin that fits your stack — or submit your own and share it with the ecosystem.

The takeaway

Agent Plugins is the interoperability floor the agent ecosystem has been missing. One manifest, one directory layout, and your skills and MCP servers work everywhere. If you maintain agent components, packaging them as Agent Plugins is the safest long-term bet — and if you're looking for components to use, the AIMCP directory is a good place to start.

---

Browse real plugins: explore the Agent Plugins directory on AIMCP to find skills and MCP servers packaged for any compatible client.