Write it

A plugin is an npm package that exports a manifest. The guide takes you from nothing to a running one; buddi plugins scaffold writes the first files.

Publish it under your own name

npm publish --provenance --access public from a public repository, so npm records where the tarball was built. Any name is fine; buddi.name in package.json is the short name it installs as.

Add one file

Fork withbuddi/buddi-market and add plugins/<name>/entry.json: npm name, version, a title, two sentences, a category, your name, the licence, the source. An icon.svg and a screenshot or two beside it if you like. The README shows the exact fields.

Run the check

node scripts/check.mjs --write <name>. It asks npm for the version, reads its provenance, stages the package the way an install would and reads its manifest, then writes what it found into the entry: tools and tiers, schema, hosts, timers, agents. The page can never claim less than the code does.

Open the pull request

The same check runs there. Merging is the review: the entry records the version that was read and what the reading covered, and the page says Reviewed. A new version is a pull request that bumps the version.

Paid plugins

Welcome. Set pricing to paid or subscription with a link to your own page; buddi shows the price line on the card and sends people to you. Nothing about payment passes through buddi or this site.

What a review is, and is not

The check verifies that the listing matches the code, and a reader looks at the code before merging. A plugin still runs inside buddi with everything buddi can do; the trust sentence on every install card stays true, and the owner still approves each install by its hash.