Submit a DSH plugin
Listings here are generated from public repository data and reviewed by hand. If you maintain a DeepSeek Harness plugin, the fastest path is to add the dsh-plugin topic and submit the URL.
- 01
Publish the repository
Make the plugin public and add the dsh-plugin topic so directories that scan GitHub discover it automatically. Include a LICENSE file and a README with the exact install command.
- 02
Declare compatibility
State the harness release you tested against in your dshTarget field and repeat it in plain language in the README, including what fails on older releases.
- 03
Send the listing request
Submit the repository URL with a one sentence description under 160 characters and the install command you want shown. Anything a reviewer should know belongs here too.
- 04
Review and listing
Submissions are checked for source, install spec accuracy, permission surface and maintenance signals. A listing appears once those four checks pass, usually the same week.
How to submit
Open an issue or send a message through the contact page with the details below. There is no form to fill in and no fee, and maintainers get the same review as anyone else.
Send these five things
- Repository URL
- One sentence description, under 160 characters
- Exact install command
- Category you think fits best
- Notes for reviewers: credentials required, paid endpoints, or unusual permissions
Review checklist
These are the six things checked before a listing appears. A submission missing any of them is usually returned with a note rather than rejected.
- Public repository with visible commit history
- dsh-plugin topic added to the repository
- LICENSE file present at the root
- README contains a copy-ready install command
- dshTarget declared, matching the release you tested
- Optional: exact version pin documented for reproducibility
What a listing does not mean
A listing is not an endorsement, and it is not a security guarantee. It records what was checked: the source, the install spec, the verification level and the maintenance signals. Users are still expected to read the permission surface before installing, which is exactly what the listings are built to make easy.
Read the editorial policy and the verification rules for the full criteria, or see the publishing guide for how to prepare a repository that passes review.