Two things ship in one repository: a plugin specification, and the official plugins written against it. Publishing both is how you demonstrate that the format is implementable rather than aspirational.
A specification alone is a document. A specification with working implementations beside it is a format other people can trust enough to build on.
The word draws a line between what the vendor maintains and what the ecosystem writes. Both sit in one repository, which makes the line visible rather than implied.
No plugin count, no API surface, no version number, no marketplace figures. The trending description publishes none, so none appears here.
Concept mock, not affiliated with the project. The plate is labelled shape only: the three conformer boxes are generic and carry no plugin names, because the repository's trending description is one line and names none. That line is "Cursor plugin specification and official plugins", read 21 August 2026.