Submission contract

Public uploads are disabled for AgentRig 2.0. Maintainers can submit one pinned upstream snapshot for registry/catalog review through trusted publishing:

agentrig plugin submit owner/repo@v1.2.3 --trustedPublish

agentrig plugin submit --trustedPublish creates a review submission from one resolved source. The source can be a tagged local checkout, a GitHub shorthand, or a GitHub repo URL plus a version tag:

agentrig plugin submit . --version v1.2.3 --trustedPublish
agentrig plugin submit owner/repo@v1.2.3 --trustedPublish
agentrig plugin submit https://github.com/owner/repo --version v1.2.3 --trustedPublish

If the plugin lives below the repo root, pass its repo-relative path:

agentrig plugin submit owner/repo@v1.2.3 --path plugin --trustedPublish

Standalone public Skill, MCP, and Hook upload flows are not part of AgentRig 2.0. MCPs and hooks should ship through plugin artifacts; selection bundles from trusted plugin artifacts remain allowed.

To check review progress later:

agentrig plugin status

You can also pass a submission id directly:

agentrig plugin status <submission-id>

The hosted web submission UI at /submit is disabled for 2.0.

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

What happens after submission

The normal path looks like this:

1. submit one exact upstream snapshot
2. AgentRig validates and scans it
3. an admin reviews it in the web app
4. approval materializes a catalog listing in AgentRig
5. the approved listing becomes installable through an AgentRig InstallBundle

A verified mirror is separate. An admin may choose Start verified mirror for an approved listing; that optional step opens or updates a PR into agentrig-registry for audit and verification.

Important boundary

Submission is not a public install source.

A submission can support:

• review
• validation
• catalog listing review
• optional verified mirroring after approval

It does not make author repos, ZIPs, arbitrary URLs, or raw Convex storage payloads installable. Only the approved listing's SDK-produced InstallBundle is exposed through the official install endpoint.

Source rules

AgentRig resolves every source to one pinned repo, tag, commit, and repo-relative plugin path.

Rules:

• GitHub sources must resolve through a real Git tag.
• Branch names, raw commit SHAs, latest, floating refs, ZIP uploads, and alternate GitHub URL shapes are not valid submission inputs.
• --path is always relative to the source repo root. . is valid for a root plugin.

Validation boundary

Submission validates at least:

• repo reachability and normalization
• tag-to-SHA consistency
• exact plugin root existence
• plugin.json presence and validity
• manifest version consistency with the submitted tag
• path safety, symlink/submodule rejection, and forbidden file types
• install surface and scan results needed for later registry artifacts

Submission statuses

The submission pipeline uses these statuses:

• pending_review
• approved
• rejected
• blocked

Validation scan status is tracked separately as pass, warn, or fail.

Approved listings also carry installability:

• available listings can be installed.
• yanked listings may remain visible for existing users, but are not offered as new installs.
• taken_down listings are removed from normal install and discovery flows.

Security notes

• Never submit sources that contain secrets.
• Review and validation reduce risk, but install trust belongs to the approved catalog listing and its AgentRig InstallBundle, not to submission itself.