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 Skills
#Plan / termChecked
1Free to read (licensing is per-skill2026-09-22
2no root license)2026-09-22

One-liner: openai/skills was OpenAI’s catalog of Agent Skills for Codex — folders of instructions and scripts agents load for specific tasks. As of 2026-09-22 its README leads with a deprecation banner redirecting everyone to openai/plugins.

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

Attribute Value Source
GitHub stars 27,528 (1,858 forks, 299 open issues+PRs) openai/skills via GitHub API, 2026-09-22
License (repo level) None at root — API license field empty; only 4 top-level entries (.gitignore, README.md, contributing.md, skills/) GitHub API + root contents, 2026-09-22
Per-skill licenses 44 LICENSE files sit inside the 44 skill folders (e.g. .curated/aspnet-core/LICENSE.txt) recursive git tree, 2026-09-22
Spot-check skills/.system/skill-creator/LICENSE.txt and .curated/gh-fix-ci/LICENSE.txt are Apache-2.0 texts (sampled, not all 44 audited) raw file fetch, 2026-09-22
Language Python GitHub API
Created 2025-11-25 GitHub API
Last push 2026-09-08 GitHub API
Deprecation (verbatim) “This repository is deprecated. For current Codex skill and plugin examples, use the OpenAI Plugins repository.” raw README, 2026-09-22
Tree contents 39 .curated + 5 .system skill folders (44 SKILL.md total); imagegen, openai-docs, plugin-creator, skill-creator, skill-installer are the .system five recursive git tree, 2026-09-22

Two corrections the 09-22 pass makes

The 09-21 review round recorded ~25.0k stars (snapshot drift; API now 27,528) and flagged “逐skill目录LICENSE.txt授权” — that licensing read is confirmed here from the tree itself. New finding: the README still tells users to install from a .experimental tier, but no .experimental folder exists in the main branch anymore (0 directories in the recursive tree). Documentation lag on a deprecated repo is expected; treat the tree, not the README, as the state.

Licensing reality

No blanket license at repo root. Individual skill folders carry their own LICENSE.txt, so “it’s on GitHub under an org account” is not a compliance answer — check the specific skill’s license file before shipping anything built on it. The sampled files are Apache-2.0, but we did not audit all 44.

The catches

  • Deprecated ≠ deleted. It still gathers stars (27.5k by 09-22, after the banner), but examples and maintenance moved to openai/plugins.
  • Per-skill licensing is more fragmented than a single root license would suggest — real work for any commercial adoption.
  • .system skills auto-install with the latest Codex per the README, so part of this catalog is quietly in your environment regardless of the banner.

Who should look at it

Codex users tracing where official skills live now, and anyone auditing skill provenance/licensing — the folder structure is a case study in mixed-license catalogs.

All facts pulled 2026-09-22 from the GitHub API, the recursive git tree, root and per-folder contents listings, and raw README/LICENSE fetches. No skills were executed; no hands-on claims are made.