Price terms as published

Each line is the vendor’s own wording, split from the price capture checked on 2026-09-22. Nothing here is rounded, converted or re-worded — the full sentences stay in the review below. Lines that carry only a price continue the plan named on the line above, in the vendor’s own order.

2 price terms for OpenAI Plugins
#Plan / termChecked
1Free to read (licensing per plugin folder2026-09-22
2no root license)2026-09-22

One-liner: openai/plugins is where OpenAI now keeps example plugins for Codex — the pattern-of-record repo the deprecated openai/skills catalog points to, covering tool plugins and skill-only plugins with a marketplace manifest.

Verified facts (GitHub API + recursive tree + raw README, 2026-09-22)

Attribute Value Source
GitHub stars 7,093 (917 forks, 39 open issues+PRs) openai/plugins via GitHub API, 2026-09-22
License (repo level) None at root — API license field empty; recursive tree has no root LICENSE (21 license files inside subfolders) GitHub API + git tree, 2026-09-22
Language JavaScript GitHub API
Created 2026-03-04 GitHub API
Last push 2026-09-18 (active week-to-week) GitHub API
Plugin count 62 plugin folders under plugins/ (each with required .codex-plugin/plugin.json; 64 manifests total, the 2 extras are plugin-eval test fixtures) recursive git tree, 2026-09-22
Marketplace default at .agents/plugins/marketplace.json; separate api_marketplace.json for API-key-login users README
Cross-reference openai/skills README deprecation banner points here (“use the OpenAI Plugins repository”) openai/skills raw README, 2026-09-22

The 09-21 review pass left this repo’s star count uncaptured; that ⚪ gap is closed with the 09-22 API value above.

What you get here

Reference plugin implementations for how a plugin packages skills, apps, MCP servers, agents, commands, and hooks for Codex — 62 folders spanning SaaS integrations (figma, notion, slack, stripe, dropbox, shopify, canva, vercel, cloudflare, datadog, sentry, temporal, zoom…), platform builds (build-ios-apps, build-macos-apps, build-web-apps, expo), and bundles you’d not expect from a vendor repo (superpowers, game-studio, public-equity-investing, life-science-research). The README highlights figma, notion, the three build-*-apps packs, expo, netlify, remotion, and google-slides as the richer examples.

The catches

  • Licensing fragmentation like the skills repo: no root LICENSE — audit the specific plugin folder (and its embedded third-party surfaces) before reusing.
  • Example-repo drift. These track current Codex plugin APIs, and those APIs moved through 2026; pin to the commit you cloned from.
  • “OpenAI official” covers the repo, not endorsement of what you build on top of it — and it does not mean the integrated services are free.
  • Third-party plugin folders are partner surfaces (figma, notion, stripe, etc.): their value depends on the vendor’s own MCP/app integrations staying current.

Who should use it

Codex plugin authors (this is the canonical starting point plus the plugin.json spec via its .agents/skills/plugin-creator), and agent-platform watchers tracking how OpenAI structures its plugin ecosystem after the skills→plugins consolidation.

All facts fetched 2026-09-22 from the GitHub API, the full recursive git tree (not truncated; 7,746 entries), and the raw README. No plugins installed or executed; no hands-on claims are made.