agent-plugins.org valid

Automatically discovered from public files. Ownership management is optional. Inclusion does not imply endorsement or publisher participation.

Manage this listing — optional · Visit publisher ↗

Claim my listing on Agent Web Map for agent-plugins.org:
1. POST https://agentwebmap.com/v1/sites/agent-plugins.org/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://agent-plugins.org/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/agent-plugins.org/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/agent-plugins.org).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory. Ownership management is optional.

Compatible Clients

**See also:** [§5 Manifest](#5-manifest) for manifest rules, [§6 Component discovery](#6-component-discovery) for fixed component locations and missing-location behavior, and [§8 Client extensions](#8-client-extensions) for client extension conventions.

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-20T18:51:08.880Z. Cached copy · Source on agent-plugins.org

---
title: Compatible Clients
description: Explore clients that support the portable Agent Plugins format and the components each client can load.
type: overview
---

# Compatible Clients



Agent Plugins clients can adopt portable component types incrementally. The
clients below document the components and MCP transports they support.

<CompatibleClients />


---
title: Agent Plugins
description: A portable package format for reusable components that extend AI agents.
---

# Agent Plugins



Agent Plugins is an open, vendor-neutral standard for packaging reusable components into portable plugins. Its version 1.0.0 specification defines a shared format for [Agent Skills](https://agentskills.io/specification) and [MCP servers](https://modelcontextprotocol.io/specification) that compatible clients can discover and load consistently.

## Why Agent Plugins? [#why-agent-plugins]

AI agent clients have developed their own plugin formats, even when plugins contain the same underlying components. Authors must rearrange or duplicate those components for each client, so a plugin packaged for one client may need adaptation before another can use it.

Agent Plugins defines a small interoperability floor for the parts that can be portable across clients. Shared components can use one predictable structure, while distribution, installation, permissions, user experience, and client-specific capabilities remain under each client's control.

## The portable package [#the-portable-package]

An Agent Plugin is a directory with a required manifest and optional components in fixed locations:

```text
my-plugin/
├── plugin.json
├── skills/
│   └── summarize/
│       ├── SKILL.md
│       ├── scripts/
│       └── references/
├── mcp.json
└── com.example.client/
    └── hooks/
```

* `plugin.json` identifies the plugin and the Agent Plugins version it targets.
* `skills/` contains Agent Skills in the format defined by the Agent Skills specification.
* `mcp.json` describes stdio, Streamable HTTP, or legacy HTTP+SSE MCP servers.
* Reverse-domain extension namespaces let individual clients add behavior without changing the portable core.

## Open development [#open-development]

Agent Plugins is openly licensed and developed in public. Its initial Technical Steering Committee includes Core Maintainers from Amazon, Cursor, Microsoft, OpenAI, and Vercel.

Proposals and technical decisions are public, and participation is open to the broader ecosystem. Use [GitHub Discussions](https://github.com/agentplugins/agent-plugins-spec/discussions) for asynchronous collaboration on ideas for new features and material changes, where proposals can establish a concrete portability need and implementer support. When synchronous collaboration on the standard is useful, join the [Agent Plugins Discord](https://discord.gg/692jE8wsmj).
…

Help agents understand your site

Optionally manage your description, publish terms for agents, review file health, measured discovery requests, publisher clicks and score history. Confirm domain control in your browser using a fresh token in your llms.txt, DNS, meta tag or well-known file. No backlink is required.

Manage this listing → · Agent and API instructions

Machine-readable: GET /v1/resolve?q=agent-plugins.org · GET /v1/domain/agent-plugins.org · this page as Accept: application/json or text/markdown · MCP lookup_domain