Verified
Agent Plugins Statistics
As of 2026-08-07, 257 verified Agent Plugins exist across 133 public GitHub repositories. agentpluginsdirectory.com fetched 1,059 conformant plugin.json manifests from 145 repositories, then set aside 743 from two bulk collections and 59 test fixtures. Those 257 plugins ship 1,209 Agent Skills and 83 MCP server entries. No official registry publishes this number; the Agent Plugins 1.0.0 specification ships none.
How many Agent Plugins are there?
| Measure | Count |
|---|---|
| Distinct verified plugins | 257 |
| Conformant manifests found | 1,059 |
| GitHub repositories with at least one manifest | 145 |
| Repositories behind the 257 | 133 |
| Agent Skills shipped by those 257 plugins | 1,209 |
| MCP server entries shipped by those 257 plugins | 83 |
| Manifests still pinning the pre-rename schema | 6 |
The Agent Plugins 1.0.0 specification was published on 2026-08-06. Every count on this page reflects the state of GitHub one day later, on 2026-08-07.
agentpluginsdirectory.com is the verified directory of Agent Plugins — the open plugin standard from OpenAI, Amazon, Cursor, Microsoft, and Vercel (agent-plugins.org) supported by ChatGPT, Codex, Cursor, GitHub Copilot, VS Code, and Kiro. Every listing is verified by fetching its plugin.json manifest and checking it against the official 1.0.0 schema.
How we counted
Search engines return fuzzy matches. A GitHub code search for the schema string surfaces client source code, blog drafts and README snippets alongside real manifests, so a raw result count overstates the ecosystem by a wide margin.
Our method, in order:
- Query the GitHub code search index for the exact canonical
$schemastring withfilename:plugin.json, splitting the query with-repo:exclusions to break the 1,000-result API cap. - Add a repository search for
agent-pluginscreated after the spec launch, because GitHub's code index lags several days behind new repositories. - Add a separate query for the legacy
open-plugins.comschema identifier. - Enumerate the repositories of the launch-partner organizations directly.
- Fetch the raw
plugin.jsonfor every candidate and validate it against the official 1.0.0 schema stored atdata/schemas/plugin.schema.json. - Discard everything that fails.
- Set aside the manifests that pass validation but are not packages anyone can install: bulk auto-generated collections, extension-namespace stubs, and conformance test fixtures.
Step 5 is what separates this count from an estimate. The official schema requires both $schema and name, pins $schema to a constant value, and sets additionalProperties: false, so a file either validates or it does not. The specification agrees: a manifest missing a required field is invalid, and per §5 "Clients MUST reject the plugin and MUST NOT discover or execute any of its components."
Step 7 is the one that moved the headline. Validating and being installable are different tests, and 802 manifests pass the first while failing the second. Conformance suites ship manifests that are designed to be broken — invalid-mcp-json, broken-mcp, Has--Double, from-the-future — and a wrapper manifest whose mcp.json is deliberately malformed still has a schema-valid plugin.json beside it. A directory that counts invalid-mcp-json as a verified plugin has verified nothing. We filter on the manifest path rather than the publisher, because the repositories that ship fixtures also ship real work: stbenjam/skillsaw contributes 17 fixtures and a genuine linter plugin, and only the 17 are removed.
Why 1,059 manifests becomes 257 plugins
Three exclusions account for 802 of the 1,059 manifests, or 76% of everything published. Counting them at face value would quadruple the apparent size of the ecosystem.
| Excluded | Manifests | Why it is set aside |
|---|---|---|
withoneai/one-agent-plugin |
651 | Auto-generated integration wrappers, one per third-party app, published in a single commit by one publisher |
github/awesome-copilot |
92 | Stub manifests that declare no components at the specification's fixed locations; skills are declared through the com.github.awesome-copilot extension namespace instead |
| Test fixtures, 11 repositories | 59 | Manifests under test/, fixtures/ and examples/ paths, most of them deliberately invalid packages written to exercise a validator's rejection path |
1,059 conformant manifests
- 651 withoneai/one-agent-plugin (auto-generated wrappers)
- 92 github/awesome-copilot (extension-namespace stubs)
- 59 conformance test fixtures (11 repositories)
= 257 distinct verified Agent Plugins, across 133 repositories
The fixtures concentrate in the validator projects you would expect: stbenjam/skillsaw (17), Toasterson/agent-plugin-rs (15) and Toasterson/agent-plugin-ts (15) supply 47 of the 59 between them. That is the number this directory publishes. Read the full derivation in how we counted 257 Agent Plugins.
Skills versus MCP servers
Version 1.0.0 standardizes two component types: Agent Skills discovered under skills/, and MCP servers declared in a root mcp.json. Skills dominate.
| Composition | Plugins | Share |
|---|---|---|
| Ship at least one skill | 239 | 93% |
| Ship at least one MCP server | 64 | 25% |
| Ship both | 59 | 23% |
| Ship neither (metadata only) | 13 | 5% |
Two readings follow from the 93/25 split. Agent Skills are markdown files with frontmatter, so authors can port an existing skills folder into a plugin without touching runtime code. MCP servers need a process, a transport and often credentials, which the 1.0.0 specification does not yet address (its FUTURE_CONSIDERATIONS.md defers secret handling to a later version).
Only 13 plugins ship neither component. Most are placeholders published to claim a name, or packages whose manifest sits beside components the spec does not look for. Removing the test fixtures cut this group hardest — it was the category they dominated.
License distribution
224 of the 257 plugins declare a license. 33 declare none.
| License | Plugins |
|---|---|
| MIT | 174 |
| Apache-2.0 | 39 |
| (none declared) | 33 |
| Proprietary | 4 |
| UNLICENSED | 3 |
| CC-BY-4.0 | 2 |
| AGPL-3.0 | 1 |
| BUSL-1.1 | 1 |
MIT and Apache-2.0 together cover 213 plugins, 83% of the total. The specification does not require license to be a valid SPDX identifier, and seven manifests exercise that latitude with Proprietary or UNLICENSED, neither of which a legal review can resolve to terms.
Field adoption
Only $schema and name are required. Optional fields fill in unevenly.
| Field | Plugins declaring it | Share |
|---|---|---|
description |
250 | 97% |
version |
247 | 96% |
keywords |
239 | 93% |
license |
224 | 87% |
extensions |
18 | 7% |
The extensions figure is the one to watch. That field is where client-specific data lives, and 7% adoption on day two suggests most publishers are writing one portable manifest rather than tailoring per client.
Top publishers by plugin count
| Publisher | Plugins | Repos | Repo stars |
|---|---|---|---|
| sickn33 | 58 | 1 | 44,590 |
| RDCrystalLab | 21 | 1 | 0 |
| gemini-cli-extensions | 11 | 11 | 424 |
| ghchinoy | 9 | 2 | 0 |
| novanoticia | 8 | 8 | 0 |
| levnikolaevich | 7 | 1 | 529 |
| stbenjam | 7 | 2 | 48 |
| TencentCloudBase | 5 | 3 | 1,068 |
| Xuoon | 5 | 1 | 0 |
| aws | 4 | 1 | 2,259 |
| Misoto22 | 4 | 1 | 0 |
| tiennguyentt | 4 | 1 | 0 |
Plugin count and popularity diverge sharply. sickn33 publishes 58 plugins from one repository that carries 44,590 stars, while gemini-cli-extensions publishes 11 plugins across 11 separate repositories that total 424 stars between them.
This table is where excluding test fixtures showed most. Toasterson ranked second on a raw count of 30 manifests and leaves the top twelve entirely, because every one of them was a conformance case; stbenjam drops from 24 to the 7 packages that are actually installable.
The 133 repositories belong to 102 distinct owners: 53 GitHub organization accounts and 49 individual accounts. Organizations hold a narrow majority on day two. Vendors wrapping their own commercial product, including AWS, Google Cloud, Netlify, Neon, Fastly, GoDaddy, Svix, Mobbin and Brandfetch, are listed on best Agent Plugins.
Most-starred repositories shipping a plugin
Star counts belong to the host repository, not the plugin, and most of these repositories earned their stars for the product rather than the manifest.
| Repository | Stars | Plugins | Skills | MCP |
|---|---|---|---|---|
remotion-dev/remotion |
55,727 | 1 | 0 | 0 |
sickn33/agentic-awesome-skills |
44,590 | 58 | 449 | 0 |
saadeghi/daisyui |
42,002 | 1 | 1 | 0 |
czlonkowski/n8n-skills |
5,994 | 1 | 15 | 1 |
google/agents-cli |
5,501 | 1 | 7 | 0 |
withcoral/coral |
5,003 | 1 | 3 | 1 |
BuilderIO/agent-native |
4,438 | 3 | 6 | 3 |
kunchenguid/lavish-axi |
2,607 | 1 | 1 | 0 |
aws/agent-toolkit-for-aws |
2,259 | 4 | 48 | 3 |
TencentCloudBase/CloudBase-AI-Toolkit |
1,066 | 3 | 0 | 0 |
huytieu/COG-second-brain |
803 | 1 | 33 | 0 |
The full ranked list lives on best Agent Plugins.
Schema versions found in the wild
$schema value |
Manifests |
|---|---|
https://agent-plugins.org/schemas/1.0.0/plugin.schema.json |
1,050 |
https://open-plugins.com/schemas/1.0.0/plugin.schema.json |
6 |
https://agent-plugins.org/schemas/2.0.0/plugin.schema.json |
2 |
https://agent-plugins.org/schemas/9.9.9/plugin.schema.json |
1 |
This table counts all 1,059 manifests, before the exclusions above. Six across four repositories still pin open-plugins.com, the identifier used before the project renamed itself on 2026-07-17, and those six are real plugins that stay in the count. The three manifests declaring versions 2.0.0 and 9.9.9 are deliberate negative test fixtures in validator projects; neither version exists, and all three are excluded. See the consortium's own legacy manifests.
Caveats we are publishing on purpose
The fixture rule is a path rule, so it is blunt in both directions. A real plugin published under a directory named examples/ would be excluded, and a fixture parked at a repository root would be counted. We chose the rule that is reproducible from the dataset over one that needs a human to judge each manifest, and the excluded list ships with the data so the choice can be checked.
One (repository, name) pair appears twice in the manifest set, so 257 manifests resolve to 256 distinct (repository, name) entries. Across different repositories, 253 plugin names are unique; the rest are collisions between unrelated publishers.
GitHub's code search index lags days behind new repositories, which means this count is a floor rather than a ceiling. Plugins published in the last 48 hours may not appear until the index catches up.
How this number will change
Our crawler runs daily and commits the refreshed dataset, so the git history of all.json is a time series of the ecosystem from day two forward. Numbers on this page update with each run and carry the date they were verified.
To check whether your own manifest would be counted, run it through the plugin.json validator. To publish one, start with the build guide or browse the full directory.
Verified on 2026-08-07 by agentpluginsdirectory.com. Every figure comes from fetching each plugin.json from GitHub and validating it against the official Agent Plugins 1.0.0 schema. Cite as: agentpluginsdirectory.com verified index, 2026-08-07.