openai/plugins

Developers can configure Codex to handle specific tools and workflows

This repository collects configuration files that help Codex perform concrete tasks, such as converting Figma designs into code or building iOS apps. Each plugin packages the necessary instructions and settings so that Codex can understand and execute specific tools or workflows. This allows developers to adjust Codex to follow their project structure or preferred working methods.

Plugin folder structure and marketplace

Each plugin resides in a plugins/<name>/ folder and includes the required .codex-plugin/plugin.json manifest file. This manifest defines the plugin's basic information and, as needed, provides additional functional modules such as skills/, .mcp.json, agents/, and commands/. The default marketplace is defined in .agents/plugins/marketplace.json and points to the standard plugins/ directory, while users logged in with an API key use a separate .agents/plugins/api_marketplace.json. This structure allows plugins to be managed independently while easily integrating into the Codex environment.

Included example plugins

The repository contains examples for various development scenarios.

• Design and knowledge management plugins/figma supports design system rules and code connections, while plugins/notion expands Codex's support to non-development tasks such as planning, research, meetings, and knowledge recording.
• Platform-specific app development plugins/build-ios-apps and plugins/build-macos-apps enable Codex to handle processes from SwiftUI implementation to refactoring, performance optimization, debugging, and packaging. plugins/build-web-apps and plugins/expo cover deployment, UI, payments, and database workflows for web and mobile apps.
• External service integration plugins/netlify, plugins/remotion, and plugins/google-slides provide additional public skills and MCP-based plugin bundles.

Pre-use considerations

This repository serves as a reference for the standard structure of Codex plugin development. Developers can create plugins tailored to their projects based on these examples or modify existing ones to adjust Codex's behavior. It is important to understand the relationship between the plugin.json manifest and accompanying files. The README does not specify compatibility with specific Codex versions or potential security policy conflicts, so you must directly verify compatibility with your current Codex version before use. It is also advisable to review whether the commands or agent settings included in the plugin conflict with your security policies or project rules.