Codex plugins: find, compare and track changes
CodexPluginStats is an independent directory of Codex plugins with saved descriptions, declared skills, available package files and before-and-after change history. Use it to research a plugin before connecting it, and to see what changed afterward.
By CodexPluginStats · Published
Where can I find Codex plugins?
Browse our Codex plugin directory by task, developer or category. Plugin pages bring together publisher descriptions, declared skills, saved files and observed changes. For installation and current availability, follow the marketplace link on the plugin page and check the requirements in your own account.
OpenAI describes plugins as packages of reusable workflows and capabilities; they can include skills and connected apps. A skill supplies instructions, while an app can connect an external service. Access can depend on your plan, workspace and region. See OpenAI’s plugin documentation.
CodexPluginStats is not an official OpenAI marketplace and does not install plugins. Our catalog reflects what our collection account can observe; it is not a guarantee of availability for every user.
How do I choose a Codex plugin?
- Start with the task. Compare code review, GitHub workflows, browser automation, PDF tools or research workflows.
- Read the declared instructions. Check the skills and available SKILL.md files to understand the workflow the publisher intends.
- Check setup and cost. Review required accounts, connections and dated pricing research. An unknown price does not mean a plugin is free.
- Review what changed. Compare saved observations to see edits to descriptions, instructions and archived files.
- Follow the plugins you use. Save up to 10 plugins on the free plan and return to Following to review their changes.
These checks help you investigate a plugin; publisher claims and saved instructions do not establish that its runtime behavior has been tested. We do not rank plugins by popularity: installation counts and active users are unavailable in our Codex source.
What does a Codex plugin change look like?
Our archive preserves the observed before and after, so you can inspect the evidence behind a change instead of relying on the latest listing alone.
A description becomes more specific
In the HireOtto comparison, the saved description changed from “Manage advertising campaigns” on September 30, 2026 to “Analyze & Manage Google Ads” on October 10, 2026. This establishes a listing edit, not a verified new capability.
A plugin is renamed
The Sunny Cars comparison shows “Sunny Cars Booking Assistant” in the September 30 observation and “Sunny Cars” in the October 9 observation.
Skill instructions and package files change
The Plugin Creator skill comparison exposes line-by-line changes to saved instructions. The PickTheHotel package comparison links to individual changed files. Text comparisons depend on archived content being available; binary and large files show metadata instead.
Observation dates describe when we saved the content, not verified release dates. Read collection-source warnings on comparisons: snapshots from different sources may not establish an actual package change.
Explore recent Codex plugin changes →Sources, coverage and freshness
Use collection coverage for current collection freshness and archive gaps, and catalog growth for dated counts. Catalog counts measure observed supply, not installs, usage or popularity.
Our sources and methodology explain collection scope. The linked comparisons above are permanent records supporting the examples in this guide. Publisher descriptions remain publisher claims.
For official product behavior, consult OpenAI’s plugin documentation (checked October 12, 2026). For Claude, use our separate Claude plugin directory; its sources and coverage differ.
You can also connect an assistant to our catalog to query the available records.