Skip to content
AGNT
All stack tools
Surface

Plugins + AGNT

Plugin patterns that survive the model swap — from Paperclip to AGNT fleets.

Official source

What it is

Plugins package skills, subagents, commands, hooks, and MCP servers into installable bundles. Drop a plugin into a Claude Code session and it brings its own capability surface — no manual config.

The interesting property: plugins are portable across sessions, teams, and model swaps. A well-shaped plugin is agent-runtime-agnostic. That's the property AGNT wants to lean on.

Where AGNT fits

  • AGNT exposes a plugin-shaped surface through Paperclip — the control plane AGNT uses to hire agents, swap adapters, and route tasks. Paperclip plugins are installable at the fleet level and every agent in the fleet inherits the plugin's capabilities.
  • Plugins that bundle skills + MCP servers port directly: AGNT's plugin loader reads the Claude Code plugin format and registers each included skill + MCP server against the AGNT runtime. One install, everything works.
  • Survive-the-model-swap: because plugins are declarative, they don't care whether the underlying model is Claude, Codex, Gemma, or Gemini. AGNT's fleet adapter layer handles the model, the plugin handles the capability.

Integration recipes

Prompts & playbooks

Links

Compose, don't compete.

AGNT plugs into the tools you already trust. See what else it composes with.