Agent Plugins: portable plugin standard for AI agents

MAIN GUIDE

A single package can combine Skills and MCP servers in a common structure that compatible clients can discover and load.

What these plugins are for

These are reusable components designed to extend what an AI agent can do for a specific job. A package may contain instructions, tools, resources, automations or connections to external services. The goal is a useful result with less setup and less repetitive work.

This guide is intended for plugin creators, agent developers, integrators and buyers of reusable AI components. Every listing should clearly explain the benefit, requirements, compatibility, installation, limitations and external costs.

Tasks they can handle

  • Package reusable instructions as Agent Skills.
  • Declare local or remote MCP connections through mcp.json.
  • Identify the package and version with plugin.json.
  • Reduce client-specific repackaging.
  • Publish structured metadata for catalogs and marketplaces.
  • Prepare a portable base for future clients and devices.

How to choose a plugin

  1. Define the exact task you want to remove or accelerate.
  2. Check what data and permissions the plugin requires.
  3. Verify compatibility with your agent and connected tools.
  4. Look for clear installation steps and examples of the final result.
  5. Test with supervision before automating sensitive decisions.

What a strong listing should include

Clear outcome

What it delivers and what problem it removes.

Compatibility

Clients, versions, tools and requirements.

Installation

Concrete steps without hidden assumptions.

Security

Permissions, data handling and external services.

Evidence

Screenshots, video and real examples.

Maintenance

Version, update date and support.

Frequently asked questions

Does the standard include an official store?

No. Distribution, registries and marketplaces are outside the specification.

Does it already work in every model?

No. Direct compatibility depends on each client implementing the format and components used.

Could it be used by robots in the future?

A robotics client could adopt the format for Skills or MCP connections, but v1 does not define physical control or robotics safety.

MARKETPLACE

Find a tool for this job.

Compare the benefit, compatibility and instructions before buying.

EXPLORE PLUGINS