openai/plugins

This repository is a curated set of example Codex plugins, not a standalone application. Its purpose is to show how a plugin is structured so that Codex can pick up additional skills, tools, and workflow surfaces, and the sample plugins double as reference implementations for people building their own.

How a plugin is organized

Each plugin sits in its own directory under plugins/<name>/ and must include a .codex-plugin/plugin.json manifest. Beyond that required file, a plugin can optionally bundle skills/, an .app.json, an .mcp.json, plugin-level agents/, commands/, hooks.json, assets/, and other supporting files (README). In practice, the manifest anchors the plugin, while the companion surfaces decide what capability it exposes—whether that is instructions/skills, MCP-backed tools, app actions, or hook and command entry points.

Discovery through marketplaces

Plugins are surfaced through a default marketplace at .agents/plugins/marketplace.json, which points at the standard plugins/ directory. Users who log in with an API key have a separate marketplace listed at .agents/plugins/api_marketplace.json (README). That means the marketplace file is the catalogue layer: adding or listing a plugin is a matter of how the marketplace entry and the plugin directory are arranged, not of changing Codex itself.

What the examples cover

The larger examples show the range of surfaces in use. plugins/figma demonstrates use_figma plus Code to Canvas, Code Connect, and design system rules; plugins/notion targets planning, research, meetings, and knowledge capture; plugins/build-ios-apps and plugins/build-macos-apps focus on SwiftUI/AppKit implementation, refactoring, build/run/debug loops, and packaging; plugins/build-web-apps covers deployment, UI, payments, and database workflows; plugins/expo addresses Expo/React Native apps, SDK upgrades, EAS workflows, and Codex Run actions. Smaller bundles such as netlify, remotion, and google-slides illustrate additional skill- and MCP-backed plugins (README).

Requirements and scope

The visible material documents the Codex plugin format and example layout but does not declare a license or state the Codex version needed for each optional surface. The repository is best read as examples to learn from and adapt: the required plugin.json manifest is clear, while whether a given plugin works depends on which optional files and external services its examples assume. No separate installation or compatibility guide is provided in the supplied README, so those details would need to be established from the plugin files themselves rather than assumed from the collection.