Agentrig
Getting Started

Getting started

Install AgentRig, connect to registries, and install your first provider plugin.

Getting started

AgentRig starts with a simple consumer flow:

  1. initialize config
  2. browse available plugins
  3. inspect a plugin if needed
  4. install it as a native provider plugin

Official registry flow

Install agentrig

Install the CLI once so you can use the same plugin workflow in any repo.

npm install -g agentrig

Initialize config

Seed a minimal config with the official registry.

agentrig init

Browse the official registry

See what plugins are available before you install anything.

agentrig search review

Inspect the plugin

Optional, but useful if you want to review dependencies, files, and trust before installing.

agentrig view agentrig/agentrig.core-committer

Install it as a provider plugin

Choose the provider you actually use in Claude Code, Codex, or Cursor.

agentrig plugin install codex agentrig/agentrig.core-committer

Third-party registry flow

Third-party registries are explicit. Add the registry first, then install plugins from it with the canonical install ref:

<registryAlias>/<namespace.plugin>

The unversioned form installs the latest installable version. Add @<version> only when you need an exact reproducibility or rollback pin.

agentrig registry add georg https://georg.dev/agentrig
agentrig search typescript --registry georg
agentrig plugin install cursor georg/georg.ts-master-plugin

What is not installable

  • direct plugin.json URLs
  • local file paths as public install refs
  • ZIP uploads
  • author repos
  • arbitrary HTTPS manifest URLs
  • Convex-hosted bytes

Use those surfaces for authoring, review, or discovery only. Public installs come from static signed registries.

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

Where to go next

On this page