Publishing plugins

AgentRig separates publishing from installability.

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

Installable publishing paths

Installable publication happens through official and reviewed registry/catalog artifacts. Maintainers approve a catalog listing and the CLI resolves installs by fetching an InstallBundle from agentrig.ai.

The verified registry mirror is a separate audit and verification lane. It is not required for catalog approval or normal public installs.

Submission and review

Public upload and the hosted /submit flow are disabled for AgentRig 2.0. Plugin proposals should go through a maintainer-reviewed GitHub issue or PR.

Maintainer-configured trusted publishing may still submit canonical snapshots for review. Submission is not itself an install source.

See: Submission contract

There are two independent lifecycles:

1. Submission lifecycle: submit, validate, review, then approve or reject. An approval materializes the catalog listing.
2. Verified-mirror lifecycle: an optional admin Start verified mirror action creates a reviewable PR into agentrig-registry for approved listings.

Being approved into the catalog does not require a GitHub PR. The only repository app used for source fetches is the read-only user-repo-sync app.

Trusted publishing from GitHub Actions

Trusted publishing lets CI submit through the same canonical review backend without storing a long-lived AgentRig token.

Flow:

• GitHub Actions requests an OIDC token with audience agentrig from a manually dispatched workflow.
• AgentRig verifies issuer, audience, event_name=workflow_dispatch, runner_environment=github-hosted, repository, repository id, owner, owner id, workflow, optional environment, SHA, ref, run id, and run attempt.
• AgentRig mints a short-lived scoped publish token.
• The CLI submits the canonical plugin snapshot through the maintainer submission endpoint.
• Catalog approval still requires review. Verified mirroring, when used, is an explicit admin action after approval.

Required workflow permissions:

permissions:
  contents: read

Example:

name: Publish AgentRig plugin

on:
  workflow_dispatch:
    inputs:
      ref:
        description: Git ref to publish
        required: true
        type: string

permissions:
  contents: read

jobs:
  publish:
    runs-on: ubuntu-latest
    environment: production
    permissions:
      contents: read
      id-token: write
    steps:
      - uses: actions/checkout@<full-commit-sha>
        with:
          ref: ${{ inputs.ref }}
      - uses: pnpm/action-setup@<full-commit-sha>
      - uses: actions/setup-node@<full-commit-sha>
        with:
          node-version: 22
      - run: pnpm dlx agentrig plugin submit "$GITHUB_REPOSITORY@${{ inputs.ref }}" --trustedPublish

Setup requirements:

• Configure the trusted publisher in AgentRig for the plugin artifact.
• Bind the exact GitHub repository, repository id, owner, owner id, workflow file, and environment if used.
• Use workflow_dispatch only for trusted publishing. Keep PR and push CI separate and read-only.
• Use GitHub-hosted runners. Self-hosted runners cannot mint AgentRig publish tokens.
• Do not publish through arbitrary reusable workflows.
• Do not restore or save dependency caches in jobs with id-token: write.
• Pin actions to full commit SHA.
• Keep plugin.json in the submitted plugin path, or pass --artifactId.
• Do not store an AgentRig access token in CI.

Self-hosted registry

Host your own static signed registry at a base URL.

Use canonical ids and install refs:

• plugin id: namespace.plugin
• install ref: <registryAlias>/<namespace.plugin>

Append @<version> only when you need an exact reproducibility or rollback pin.

Recommended next steps:

• Hosting a registry
• Team registry guide

Directory listing

The directory is a curated list of registries published at https://agentrig.ai/directory/index.json.

Directory listing is for:

• Discovery on the AgentRig homepage
• awareness of registries that exist

It is not an upload mechanism and not an install-trust mechanism.

Contribute to the official registry

To submit a plugin for catalog review and understand the separate verified mirror workflow, follow the official registry workflow.