OpenAI's Plugin Marketplace Is Quietly Filling Up With Vendors
openai/plugins gained 505 stars yesterday and sits at 6,161, which is a strange trajectory for a repo that mostly contains JSON. What it holds is the format Codex plugins ship in, plus a curated marketplace file that has been steadily accumulating names: Qodo went in on Monday, CrowdStrike's Foundry and Fusion late last month, alongside Figma, Notion, Netlify, Expo, Remotion, and Google Slides.
The shape of the format is the news. A plugin is a directory with a required .codex-plugin/plugin.json manifest and optional companions: skills, an .mcp.json, an .app.json, plugin-level agents and commands, a hooks.json, and assets. Look at that list and you can see the consolidation happening. Skills, MCP servers, slash commands, and hooks were four separate ecosystems a few months ago, each with its own repos and its own trending week. Here they are four optional folders inside one installable unit.
That matters more than any single plugin, because it settles an argument by shipping. OpenAI deprecated its standalone skills repo back in June, and plenty of people read that as the skills idea losing. It was not; skills got demoted from a format to a field. The distribution unit is now the plugin, and the marketplace file, .agents/plugins/marketplace.json, is where curation lives, with a separate API-key marketplace next to it.
Which means the interesting question is no longer whether skills win. It is who runs the shelf. Community skill repos have been owning GitHub trending for months (https://clauday.com/article/e3d92bdf-4f28-4492-9d9d-dce2e7ffcb3a) while vendors quietly queue up for a slot in a JSON file that one company merges pull requests into. https://github.com/openai/plugins
← Back to all articles
The shape of the format is the news. A plugin is a directory with a required .codex-plugin/plugin.json manifest and optional companions: skills, an .mcp.json, an .app.json, plugin-level agents and commands, a hooks.json, and assets. Look at that list and you can see the consolidation happening. Skills, MCP servers, slash commands, and hooks were four separate ecosystems a few months ago, each with its own repos and its own trending week. Here they are four optional folders inside one installable unit.
That matters more than any single plugin, because it settles an argument by shipping. OpenAI deprecated its standalone skills repo back in June, and plenty of people read that as the skills idea losing. It was not; skills got demoted from a format to a field. The distribution unit is now the plugin, and the marketplace file, .agents/plugins/marketplace.json, is where curation lives, with a separate API-key marketplace next to it.
Which means the interesting question is no longer whether skills win. It is who runs the shelf. Community skill repos have been owning GitHub trending for months (https://clauday.com/article/e3d92bdf-4f28-4492-9d9d-dce2e7ffcb3a) while vendors quietly queue up for a slot in a JSON file that one company merges pull requests into. https://github.com/openai/plugins
Comments