GitHub: purpose and common use cases
GitHub is represented as a plugin from openai/plugins. Its catalog record points to plugins/github and is grouped under Developer Tools, Development, and Code Review; install and source links are kept separate so the directory does not imply capabilities that are not present upstream.
Where GitHub fits in an agent workflow
GitHub is a Codex plugin associated with developer tools. For GitHub, the plugin layer sits one level above individual skills: they can package capabilities, integrations, MCP connections or supporting resources into one installable unit. For discovery, GitHub is most relevant to github, git, and repositories. The GitHub plugin page is useful when you are choosing an integration first and then deciding which bundled capability to use.
What to check before using GitHub
Before enabling GitHub, check the source-backed metadata below for authentication, version, license and included capabilities. This record is tied to plugins/github; the GitHub upstream manifest remains the authority for installation requirements and behavior. Artifiner uses the GitHub page to make comparison easier, not to replace the vendor or repository documentation.