Codex Extensions: skills, plugins, MCP, hooks and workflows
Use this hub when you know you want to extend Codex but have not yet decided whether the job calls for a skill, plugin, MCP connection, hook or workflow. Artifiner organizes each capability type separately while keeping their relationships visible.
Choose the right extension type
Use a skill for task-specific instructions, a plugin for a packaged integration, MCP when the agent needs external tools or data, a hook for event-driven automation, and a workflow when the task needs a repeatable sequence.
Why the distinction matters
Two capabilities can solve similar problems while having very different installation, permissions and maintenance requirements. Separating entity types makes comparison clearer and prevents every integration from being reduced to the vague label “extension.”
Built to expand beyond one ecosystem
Artifiner uses a neutral capability model so the catalog can add future agent ecosystems without changing the underlying distinction between instructions, integrations, connections and automation.
Explore Codex extension types in one catalog
Search the source-backed catalog, refine by category or provenance, and open an entity page for installation, compatibility and upstream verification.