LIFEHUBBER
Choose theme

AI Visuals

OpenAI Plugins

GitHub stars: 7.4K GitHub forks: 957 Last pushed October 8, 2026: Pushed today
Stats from GitHub

The OpenAI plugins repository contains Codex plugin examples: manifests and optional skills, app connections, MCP servers, agents, commands, hooks and assets.

Use it as a developer reference for packaging a Codex extension. The repository describes plugin examples, rather than the former ChatGPT plugin system. Use this as a first read, not a recommendation. Open the original project before trusting details like terms, limits, privacy, cost, setup, or safety.

What it is

Examples of Codex plugin bundles

Each example lives in plugins/<name>/ and requires a .codex-plugin/plugin.json manifest. Companion folders and configuration files add the capabilities that example uses.

Why it stands out

The bundle can combine several surfaces

A plugin can package skills alongside app or MCP connections, commands and other supporting pieces. The required manifest and optional pieces show how a small extension can grow without starting with every integration.

Availability

Public repository and marketplaces

The README points to a default marketplace and a separate marketplace for API-key login users. Inspect the example files and access setup before using a bundle in your own Codex environment.

Why it matters

What makes it useful

If a recurring Codex task needs both instructions and an external tool, these examples show how to package those pieces together. A builder can inspect the bundle rather than distributing its instructions and connection settings separately.

Notable points

What stands out

The default marketplace is .agents/plugins/marketplace.json; API-key login users have .agents/plugins/api_marketplace.json. Those are separate catalog paths, so an example's presence in one is not enough to assume it appears in the other.

Before using

What to review

Start with the files in the specific example you want to adapt, including its manifest and any connection configuration.

Check the current Codex setup and login path against the repository's marketplace instructions.

Review the instructions, executable hooks and tool connections a bundle includes before granting access to private files or external accounts.

Reader fit

Who may find it relevant

Builders creating or adapting Codex plugin bundles.

Teams inspecting how reusable instructions and tool integrations are packaged.

Readers seeking a ready-to-use chatbot or information about historical ChatGPT plugins should use a different starting point.

Editorial note

Why LifeHubber lists it

The richer examples cover different jobs: Figma combines design-system material with tool connections, while the iOS bundle centers SwiftUI work. Choose an example by the task and companion files you need, rather than copying the largest bundle as a default.

Source links

Source materials

Reader note

Before relying on this entry

LifeHubber lists entries to help readers inspect AI projects, not to endorse them or prove they are safe, suitable, accurate, maintained, or right for a specific use. We do not verify every entry in depth. Before relying on anything listed, review the original materials, terms, privacy practices, limits, and risks that matter for your situation.

What to explore next

Inspect the skills inside a plugin.

A plugin's manifest describes a bundle, but its skill instructions and dependencies deserve their own inspection before you connect the bundle to work.

Advertisements

Advertisements

For project maintainers

Listed here? You can use the badge.

If you maintain a project with a current LifeHubber listing, you may add the optional “Listed on LifeHubber AI Resources” badge to its README, docs, or website. No introduction or permission request is needed.

See what’s moving