Agentrig
Integrations

Integrations

Install resolved plugins as native plugins for supported providers.

Integrations

AgentRig can take a resolved plugin and install it as a native plugin for:

  • Claude Code
  • Codex
  • Cursor

Consumer flow

agentrig plugin install <provider> <registryAlias>/<namespace.plugin>
agentrig plugin uninstall <provider> <registryAlias>/<namespace.plugin>

Use plugin install for the full bundle. Use selection install when you only want specific skills, MCPs, or hooks from that bundle:

agentrig install <provider> <registryAlias>/<namespace.plugin> \
  --pick skill:<name> \
  --pick mcp:<name>

Selection install materializes an AgentRig-managed Selection Bundle. The provider receives only the selected artifacts that pass SDK closure checks.

Standalone skills can be installed without --pick:

agentrig skill install <provider> <registryAlias>/<namespace.skill>
agentrig skill uninstall <provider> <registryAlias>/<namespace.skill>

Standalone MCP and hook installs without --pick are not a public V1 flow. MCPs and hooks are installed as plugin contents with --pick.

Public install refs are registry-only and latest-first by default:

  • agentrig/agentrig.core-committer
  • georg/georg.ts-master-plugin

Add @<version> only when you need an exact reproducibility or rollback pin. Install ledgers record the concrete resolved version and snapshot digest either way. Direct plugin.json paths, arbitrary URLs, ZIPs, and author repos are outside the public install contract.

Author flow

If you are publishing or testing local plugins, export provider-native marketplaces from plugin directories:

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

agentrig plugin export --agent <provider|all> --pluginsDir registry/plugins

On this page