Plugin structure

Every plugin requires a root plugin.json. A README is recommended but not required.

AgentRig plugin manifests are Agent Plugins 1.0.0 conformant. AgentRig-specific fields live under extensions["ai.agentrig"].

Common layout

plugin-name/
  plugin.json
  skills/
    <skill-name>/
      SKILL.md
      scripts/
  mcp.json
  ai.agentrig/
    scripts/
    agents/
    commands/
    hooks/
      hooks.json
    lsp.json

Notes

• skills/ and root mcp.json are the only portable Agent Plugins v1 component locations. Each skill is an immediate child directory containing SKILL.md; clients do not recursively discover deeper skills.
• mcp.json uses https://agent-plugins.org/schemas/1.0.0/mcp.schema.json. Missing portable component locations are valid; malformed component locations do not redefine the package layout.
• ai.agentrig/ contains AgentRig-specific components such as commands, hooks, agents, rules, and LSP settings.
• Provider emitters translate AgentRig-specific components into each provider's native layout.

The SDK rejects package paths that escape the resolved plugin root. New source packages cannot use .plugin/plugin.json, inline component paths, or x-agentrig; those belong to the pre-v1 contract only.

Use agentrig plugin create to scan a directory and generate a matching plugin.json.