Get your plugin listed

The registry collects itself. In most cases you do not submit anything, you tag something.

Tag your repository

Add dsh-plugin to your GitHub repository topics. The collector runs daily and will pick it up on the next pass.

On GitHub

  1. 1 Open your repository and click the gear icon beside About.
  2. 2 Add dsh-plugin to the topics field.
  3. 3 Save. Nothing else is required.
github.com/topics/dsh-plugin

Or publish to npm

Packages carrying dsh-plugin in their keywords are collected the same way. Doing both links the two into a single entry with stars and download counts together.

package.json
{
  "name": "dsh-plugin-your-thing",
  "keywords": ["dsh-plugin", "deepseek-harness"]
}

What makes a good entry

The collector reads metadata, not your README. These four fields are what a reader sees on the card.

  • A description that says what the plugin replaces or adds, in one sentence.
  • Topics beyond dsh-plugin, since categories are inferred from them.
  • A licence file, which is one of the signals behind the verified badge.
  • A README that shows the config block, because that is the first thing anyone looks for.

Something missing or wrong?

Use this if your plugin has not appeared after a couple of days, or if an entry needs correcting. It opens a pre-filled issue on the site repository. Nothing is sent from this page.

The npm package name, or the repository name.

The GitHub URL, if there is one.

Optional, if published.

What is wrong, or what the collector missed.

This form does not send anything. It builds a GitHub issue link from what you type. You review it on GitHub before anything is posted.

When it will show up

The collector runs once a day. A newly tagged repository appears within about twenty four hours, along with its stars, licence and inferred categories.

Getting removed

Remove the topic and the keyword, and the entry drops out on the next run. If you need it gone faster, open an issue.