OpenAI Plugins: Example Codex Plugin Collection
/plugins
Reach for this repo if you're building a Codex plugin and want a real, working reference for the manifest layout and how skills, MCP servers, and hooks fit together in one bundle. Skip it if you're not on OpenAI Codex, or you expected a maintained framework - these are examples you copy and adapt, and the README is short on step-by-step setup.
Official Examples of a Codex Plugin's Shape
OpenAI Plugins is OpenAI's official collection of example plugins for Codex. Per the README, each plugin sits under `plugins/<name>/` with a required `.codex-plugin/plugin.json` manifest and optional companion surfaces: a `skills/` folder, `.app.json`, `.mcp.json`, plugin-level `agents/`, `commands/`, a `hooks.json`, and `assets/`. A default marketplace at `.agents/plugins/marketplace.json` points at the `plugins/` directory, and API-key login users get a separate marketplace at `.agents/plugins/api_marketplace.json`.
A Spec Doesn't Show How the Pieces Fit Together
OpenAI Plugins exists because a Codex plugin has a specific shape - a `.codex-plugin/plugin.json` manifest, plus optional folders for skills, MCP configs, agents, commands, and hooks - and reading a spec doesn't tell you how those pieces combine in practice. Developers building their first plugin need concrete, working examples to copy from, and a marketplace file that shows Codex where to find them. This repo supplies both.
plugin.json, Skills, MCP, and Marketplace Files
- โEach plugin lives under `plugins/<name>/` with a required `.codex-plugin/plugin.json` manifest
- โOptional companion surfaces per plugin: `skills/`, `.app.json`, `.mcp.json`, `agents/`, `commands/`, `hooks.json`, and `assets/`
- โA default marketplace at `.agents/plugins/marketplace.json` that points Codex at the `plugins/` directory
- โA separate `api_marketplace.json` for API-key login users
- โRicher worked examples the README highlights: figma, notion, build-ios-apps, build-macos-apps, build-web-apps, and expo
- โAdditional skill- and MCP-backed bundles for netlify, remotion, and google-slides
Copying Figma, Notion, or Expo as a Starting Point
- โขLearning the required `plugin.json` manifest layout before writing your own Codex plugin
- โขCopying a working example - figma, notion, or expo - as a starting scaffold
- โขSeeing how skills, MCP servers, agents, commands, and hooks combine inside one plugin
- โขSetting up a plugin marketplace file so Codex can discover a team's plugins
Adapting an Example Instead of Starting Blank
You open `plugins/<name>/`, read its `.codex-plugin/plugin.json` manifest, and adapt the example to your own plugin - reusing the same folder structure for skills, MCP configs, agents, commands, and hooks. The README points to the Figma, Notion, and Expo plugins as the fuller examples to study first. Beyond the directory layout and marketplace files, the README does not document a detailed run-through, so treat the repo as a reference to copy from.
Browsing the Repo โ the README Skips the How-To
The README doesn't spell out install commands. In practice you browse or clone the repo, and the marketplace file at `.agents/plugins/marketplace.json` is what points Codex at the `plugins/` directory. A separate `api_marketplace.json` covers API-key login users. Exact step-by-step setup - how you register the marketplace with Codex - is not clearly documented in the README, so check the Codex docs for the current flow.
Documentation by Example, From OpenAI Itself
It's an official OpenAI repository - which matters because it defines, by example, what a valid Codex plugin looks like. As Codex's plugin and marketplace model takes shape, the repo doubles as documentation-by-example: the README calls out richer bundles for Figma, Notion, iOS and macOS app building, web apps, and Expo, so developers can see full plugins rather than a bare manifest.
Real Plugins to Copy, Not Just a Bare Spec
- โIt's the official OpenAI reference, so the manifest format matches what Codex actually expects
- โConcrete, varied examples rather than a bare spec - you can copy a real plugin and edit it
- โShows the full plugin surface (skills, MCP, agents, commands, hooks) in one place
- โThe marketplace files give you a working discovery setup to copy instead of guessing the format
Examples to Adapt, Not a Maintained Framework
- โณThe license isn't stated in the metadata provided, so reuse and redistribution terms are unclear - confirm on the repo before copying code into your own project
- โณThe README is short and doesn't give step-by-step install or usage instructions
- โณIt's only useful inside the OpenAI Codex ecosystem - the plugin format doesn't port to other agents
- โณThese are examples, not a maintained framework or library; you adapt them yourself and own the upkeep
Anthropic Agent Skills and superpowers
For Developers Building on the Codex Plugin System
Developers building or evaluating a Codex plugin, and teams that want a working marketplace file to standardize how their plugins are discovered. If you're not using OpenAI Codex, or you wanted an installable, maintained tool rather than a set of examples to copy and adapt, this repo won't fit.
OpenAI Plugins FAQ
OpenAI Plugins is OpenAI's official repository of example plugins for Codex, its coding agent. Each plugin sits under `plugins/<name>/` with a required `.codex-plugin/plugin.json` manifest and optional folders for skills, MCP configs, agents, commands, and hooks.
It's a collection. The repo is a curated set of example Codex plugins plus the marketplace files that let Codex find them - not a single application you install and run.
The README doesn't give explicit install commands. The marketplace file at `.agents/plugins/marketplace.json` points Codex at the `plugins/` directory, with a separate `api_marketplace.json` for API-key login users. The exact registration flow with Codex is not clearly documented here - check the Codex docs.
A required `.codex-plugin/plugin.json` manifest, and optionally a `skills/` folder, `.app.json`, `.mcp.json`, plugin-level `agents/` and `commands/`, a `hooks.json`, and `assets/`.
The README highlights figma, notion, build-ios-apps, build-macos-apps, build-web-apps, and expo as the richer examples, plus netlify, remotion, and google-slides as additional skill- and MCP-backed bundles.
Is plugins worth your time?
ChatGPT, Claude and Perplexity can all read this page. Ask one of them what it makes of plugins.