Agent skills (reusable instructions for an AI agent) and tool settings tend to be installed by hand, one at a time, differently in each tool. Agent Plugins is an attempt at one installable bundle for both, and on 12 October 2026 its maintainers asked the Agentic AI Foundation, a vendor-neutral home for agent standards, to take it in as a Growth-stage project. The proposal claims it already works in many tools. Watch: a neutral home and a licence other vendors can accept decide whether it becomes common ground. If you distribute skills, keep them in plain folders and treat the plugin wrapper as replaceable.
What it is
The proposal calls it "an open, vendor-neutral standard for packaging reusable components". A plugin can bundle agent skills and MCP server configurations, and clients can add their own extension namespaces. Version 1.0.0 of the specification is published and 1.1.0 is a working draft. The five core maintainers come from Amazon, Cursor, Microsoft, OpenAI and Vercel, and the lead, Jonathan Hefner of Vercel, filed the application.
The claim, and the licence question
The proposal says plugin support has shipped in VS Code, Cursor, GitHub Copilot, ChatGPT and Codex, Kiro and several smaller agents. It links documentation for every client it names except one, Grok Bot. Its conformance test covers only one client end to end, so "supported" here does not mean certified.
The licence question is the live debate. The software and schemas are Apache-2.0, the specification text and documentation are CC-BY-4.0, and the example repository is MIT. On 16 October the foundation's technical chief, Manik Surtani, wrote that "CC-BY-4.0 is not an appropriate spec license", asked whether the project wants to be recognised as a specification, and suggested a community specification licence. The lead maintainer replied that the licences follow MCP's choice and that any change would need committee approval and legal review. I could not see how that exchange ended.
Where it stands
The proposal moved to a governing-board vote on 20 October, and the technical committee approved it as a Growth-stage project on 27 October. Board review and a contribution agreement, which is still unsigned, remain.
What to do
Watch. Licence terms decide whether other vendors feel safe building on a format. Keep skills in plain folders so the wrapper can change.