#1006 Adopt Agent Plugins 1.0

Adopt Agent Plugins 1.0

Why this matters

Agent Plugins 1.0 is an open, vendor-neutral standard for packaging reusable Agent Skills and MCP servers so they can be discovered and loaded consistently across compatible clients.

Adopting the standard would make this plugin easier to consume across GitHub Copilot, Codex, Cursor, VS Code, and other compatible clients without requiring client-specific repackaging or duplicated component structures.

Resources:

Requested changes

Please update this plugin to conform to the Agent Plugins 1.0 specification:

Move plugin.json to the root of the plugin directory.
Add the $schema field:

{
    "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json"
  }

Align the manifest fields with the Agent Plugins 1.0 schema.
Place portable Agent Skills under the plugin-root skills/ directory.
Place MCP server configuration in the plugin-root mcp.json file, where applicable.
Use the com.github.copilot/ namespace for GitHub Copilot-specific components and metadata that are outside the portable Agent Plugins contract, such as agents, hooks, instructions, and extensions (including canvases).

The intended structure is similar to:

plugin/
  ├── plugin.json
  ├── skills/
  │   └── <skill>/
  │       └── SKILL.md
  ├── mcp.json
  └── com.github.copilot/
      └── <GitHub Copilot-specific components>

Compatibility considerations

If this repository also supports Claude Code's plugin format, please retain the Claude-specific manifest and layout as needed. Claude Code does not currently support the Agent Plugins 1.0 specification, so .claude/plugin.json may still be required for Claude Code compatibility.

However, the portable Agent Plugins manifest should live at the plugin root, and portable components should follow the standard locations described in the specification.

If the current plugin uses a non-standard location for any of the following, please consider moving or exposing them through the standard layout:

Skills should be discoverable under the plugin-root skills/ directory.
MCP configuration should be available through the plugin-root mcp.json file.
Client-specific files should be placed under the appropriate reverse-domain namespace, such as com.github.copilot/.

This would allow the plugin to support multiple clients while preserving any existing client-specific integrations.

Follow-up acceptance criteria from #1164

PR #1164 introduces a temporary legacy Codex compatibility layer. Its documented migration plan calls for removing most duplicated manifests and custom parity/shape validation. This issue should include that cleanup rather than leave the compatibility layer permanent.

Remove the legacy Codex manifest duplication and custom parity/shape validation made unnecessary by Agent Plugins 1.0, while preserving compatibility requirements for other hosts.
Prefer native Codex runtime checks over reimplementing its parser, retaining explicit repository-policy checks and only narrowly justified host-specific validation.
Retain native integration coverage for marketplace installation, the full plugin skill inventory, and MCP discovery/transport.