Consensus: purpose and common use cases
Consensus is represented as a plugin from openai/plugins. Its catalog record points to plugins/consensus and is grouped under Education & Research and Research; install and source links are kept separate so the directory does not imply capabilities that are not present upstream.
Where Consensus fits in an agent workflow
Consensus is a Codex plugin associated with education & research. For Consensus, 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, Consensus is most relevant to consensus and education & research. The Consensus plugin page is useful when you are choosing an integration first and then deciding which bundled capability to use.
What to check before using Consensus
Before enabling Consensus, check the source-backed metadata below for authentication, version, license and included capabilities. This record is tied to plugins/consensus; the Consensus upstream manifest remains the authority for installation requirements and behavior. Artifiner uses the Consensus page to make comparison easier, not to replace the vendor or repository documentation.