About

What this is

The Agent Plugins Directory is a catalogue of plugins built on the Agent Plugins open standard: skills an agent can load, and MCP servers it can call. One address per plugin, one page per skill, and the prose on every page was written by the person who published the plugin.

It exists because the standard produced packages faster than anybody could keep track of them. A plugin is a repository somewhere, and a repository is only findable by whoever already knows it is there. This site is the index that was missing.

Who runs it

Ronny Badilla, working from Costa Rica. This is an independent project, not a company, and not a product with a team behind it. When this site says it did something, one person did it.

The directory is unaffiliated with the steering committee of the Agent Plugins standard. It indexes what that standard produced; it does not speak for it, and nothing listed here has been endorsed by it.

How a plugin gets listed

Nothing is submitted and nothing is approved. An indexer reads public repositories on GitHub, validates what it finds against the specification, and lists what conforms. A plugin appears here because it was published, not because anybody asked for it to appear.

That also means a page exists only once something exists to hold it. An address that answers nothing is usually a plugin that has not been published yet, or one that was renamed after this page was built.

What the directory will not do

It never executes plugin code. The indexer reads and validates files over the GitHub API and stops there — nothing in a package is run, at index time or at any other time.

It keeps no copy of a package's files. What a page shows you is what a file contains, pinned to the commit it was read at, linked at the repository it lives in. A client that installs a plugin downloads it from its source, never from here.

What it serves to agents

Everything here is readable by a program without scraping a page. Every address answers markdown when asked for it, the whole corpus is one fetch away, and the machine-readable surface is described in an OpenAPI document. None of it requires a key or an account.

This is not a side feature. The directory catalogues tools for agents, and a catalogue of tools for agents that only a browser could read would be a strange thing to have built.

Corrections and removals

If something here is wrong about your plugin, or you want it out of the catalogue, one mail is enough and no justification is needed. The same address answers questions about publishing, about the standard, and about how a particular listing was built.

Contact

Anything on this page, and anything else, goes to info@ronnybadilla.com. There is more on the contact page, and what the site does with a reader is on the privacy page.