skills add, or import the Codex Plugin folder format. Every path
shows an immutable compatibility Preview before installation.
What you will do
Open Hub, discover or import a Plugin, preview what Rudder can use, install it into an Organization, and finish any Agent or MCP setup.Before you start
Prepare a folder containing.codex-plugin/plugin.json and at least one Skill
or supported MCP definition. Do not place credentials in the manifest or MCP
configuration; use environment references and finish authentication through
Rudder’s Managed MCP settings.
Install and set up
- Select Hub in the Primary Rail and open Plugins.
- Open one curated Plugin, use URL Import with a public source such as
coreyhaines31/marketingskills, or choose Import and then Plugin folder or Plugin ZIP. You can also add a Local marketplace or Pinned GitHub marketplace. - Preview package identity, digest, Skills, MCP definitions, App references, executable Skill files, and unsupported surfaces such as browser extensions, scheduled-task templates, and hooks. Inspection executes nothing.
- Resolve any Skill collision explicitly: keep the existing Skill, replace it, or install both by renaming the Plugin copy. Then install the package into the current Organization.
- For Skills, choose Add to Agent and select the Agents that should use them.
- For MCP definitions, choose Set up, then continue authentication, activation, and Agent access in Managed MCP settings.
- Open Local Apps directly from Hub > Plugins. Codex
.app.jsonaliases are preserved but are not executable Rudder Local Apps. - If an active Managed MCP connection exposes an HTML UI resource, open it from the MCP component. Rudder renders it in a network-disabled sandbox.
npx, package hooks, or Skill
scripts. Marketplace policy is provenance, not installation authority; an
INSTALLED_BY_DEFAULT entry still requires an explicit install action.
