Hosting a registry

A registry is a static folder that contains:

registry.json
plugins/<namespace>/<plugin>/plugin.json
plugins/<namespace>/<plugin>/versions/<version>/**
skills/<namespace>/<skill>/skill.json
mcps/<namespace>/<mcp>/mcp.json
hooks/<namespace>/<hook>/hook.json
advisories.json

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

Minimum requirements

registry.json at the registry root.
One canonical history file per artifact under its kind root.
One immutable version tree per published release under <kind-root>/<namespace>/<artifact>/versions/<version>/.
Signed registry.json plus canonical AGENTRIG_SOURCE.json, AGENTRIG_LOCK.json, and AGENTRIG_REVIEW.json artifacts for each published version.

Example

https://example.com/registry/
  registry.json
  advisories.json
  plugins/
    acme/
      infra-safety/
        plugin.json
        versions/
          1.4.2/
            plugin.json
            AGENTRIG_SOURCE.json
            AGENTRIG_LOCK.json
            AGENTRIG_REVIEW.json
            skills/infra-safety/SKILL.md
  skills/
    acme/
      review/
        skill.json
        versions/1.0.0/.skill/skill.json

Test locally

Start any static server at the registry root and add it as a registry:

agentrig registry add example https://example.com/registry
agentrig plugin install codex example/acme.infra-safety@1.4.2

For Marketplace QA smoke tests, use a separate staging registry alias and repo, not the production agentrig alias:

agentrig registry add agentrig-staging https://raw.githubusercontent.com/agentrig/agentrig-registry-staging/main
agentrig plugin install codex agentrig-staging/regenrek.test-submission

Test fixture namespaces such as regenrek.test-*, test-*, and qa-* must stay out of the production registry.

Hosting a registry

Hosting a registry

Minimum requirements

Example

Test locally

On this page