Evaluate migrating reusable tooling to Agent Plugins

[Perdolique]

Context

Agent Plugins 1.0 defines a portable package format for Agent Skills and MCP servers. Codex CLI now supports Agent Plugins manifests, Git-backed marketplaces, and workspace plugin publishing.

This repository currently distributes its own and third-party skills through vpx, while several remote MCP servers are configured separately in non-standard/codex/config.toml. A versioned plugin could give the repository a clearer release unit and update path, but installation and updates are client-managed rather than guaranteed by the portable specification.

Scope

• Inventory the repository and classify assets as portable Agent Plugin components, Codex-specific extensions, or out of scope.
• Prototype a versioned plugin containing the repository-owned skills under skills/.
• Evaluate whether any related MCP configuration belongs in mcp.json; do not duplicate third-party plugins or embed credentials.
• Decide whether this repository should also expose a Git-backed Codex marketplace via .agents/plugins/marketplace.json.
• Define the release process: Semantic Versioning, CHANGELOG.md, Git tags/releases, installation, and marketplace refresh/update behavior.
• Verify discovery, installation, skill loading, MCP loading where applicable, and version updates using a clean temporary CODEX_HOME.
• Document the migration path and retain the existing bootstrap until the replacement is verified.

Initial candidates

• Strong candidate: repository-owned skills.
• Needs evaluation: remote MCP entries that are meaningfully coupled to those skills.
• Prefer upstream: Cloudflare skills and MCP through the maintained upstream/curated plugin if it fully replaces the current setup.
• Keep outside portable v1: AGENTS.md, general Codex config.toml settings, command rules, third-party skill installation, and Playwright CLI/browser installation.

Acceptance criteria

• A documented decision matrix for each current asset.
• A minimal installable plugin and marketplace entry, or a documented reason not to adopt them yet.
• Verified Codex commands for install, list, load, marketplace refresh, and update.
• A defined version and changelog workflow with the actual update semantics documented.
• No loss of the currently selected skill set or working MCP access during migration.

References

• Agent Plugins overview
• Build an Agent Plugin
• Plugin manifest
• MCP servers
• Compatible clients