Preface¶
DeepSeek Harness (dsh) treats models, tools, sessions, sandboxes, and interfaces as plugins, with the official repository’s slogan being “Everything is a plugin”. The developer preview phase is iterating rapidly, and repositories tagged with the dsh-plugin topic are popping up on GitHub: visuals, TUI, sidebars, memory, workflows, all looking like they can be installed directly. When actually getting hands-on, the problem is rarely “are there any plugins”, but rather “which repository actually has a bundle manifest, which install command should I copy, and whether the license is usable”.
The community catalog is not an official app store for DeepSeek / HyperMind, and has no affiliation with the official repository. dsh-plugins does something different: it automatically discovers candidate repositories from GitHub topics, performs basic bundle validation, and then lists the passing entries on its website and command line for easy searching, filtering, and copying of the latest version’s install command. Inclusion does not mean official endorsement.
This article is collated after checking against the plugin catalog page, GitHub repository README, package.json, synchronization scripts, and the site dsh-plugins.org.
What is this¶
dsh-plugins is a community-maintained navigation catalog for DeepSeek Harness plugins, maintained by lwmxiaobei, with its repository at lwmxiaobei/dsh-plugins, licensed under MIT, and primarily written in JavaScript. The community plugin catalog page categorizes it under “Workflow and Automation”, with 3 GitHub stars.
It does not solve the problem of attaching another set of tools to the current dsh process, but instead compiles “where to find plugins, which repositories pass the basic manifest check, and how to write install commands” into a searchable catalog. The repository README makes this clear: this repository only saves navigation data, documentation, and maintenance scripts, and does not copy or embed any third-party plugin source code. The root package.json also does not declare dsh.bundle.patch, which is not the same type of “installable bundle” that it requires when indexing other plugins. Daily use is closer to opening the website, or running its built-in command line locally.
The mapping can be viewed as follows:
- Official runtime: deepseek-ai/deepseek-harness, start the Web UI with npx @deepseek-ai/dsh web.
- This project’s website: dsh-plugins.org, with both Chinese and English pages available.
- Machine-readable catalog: catalog/plugins.json in the repository; all candidates and reasons for exclusion are in catalog/repositories.json.
The snapshot timestamp of catalog/plugins.json is 2026-08-17T02:34:27.566Z, with a count of 609, meaning that was the number of plugins that passed the basic bundle manifest check at that time. The site homepage showed 475 entries when viewed, and the number will change with synchronization and deployment; use the update time on the corresponding page when citing.
Core Features¶
Discover from GitHub topics and perform basic bundle validation¶
The synchronization program scans GitHub’s dsh-plugin topic. Repositories entering the catalog must meet all of the following requirements:
- The root package.json declares dsh.bundle.patch
- The corresponding patch file actually exists
- The repository is not archived, disabled, or a template
Candidates that fail these conditions will be written to catalog/repositories.json along with the reason, such as missing package.json, invalid manifest, archived, or a template. This is structural validation, not a security audit or runtime compatibility test.
The GitHub Search API returns a maximum of 1000 entries per request. The synchronization script includes this limitation: if there are more than 1000 repositories under the topic, the current catalog is not a complete snapshot.
Search, filter, and view bilingual details on the website¶
dsh-plugins.org offers a Chinese homepage, with the English page at /en. The list supports filtering by keywords, language, and license, and can be sorted by most stars, most recent update, or name.
Clicking into the detail page shows:
- Install command (follows the upstream default branch, pulls the latest version at runtime)
- Package name, version, programming language, license, stars
- Catalog validation commit: only marks the catalog snapshot at that time, not a fixed commit for you to install
- Upstream repository link
The common format of install commands on the site is:
dsh plugin --profile web add github:owner/repo
The site FAQ also clarifies: this command does not include a commit hash; the commit shown on the detail page is only used to identify the catalog validation snapshot.
Preview installs via the command line, do not execute upstream code by default¶
After cloning the repository, you can use the built-in CLI. bin/dsh-plugins.mjs supports list, search, info, and install. The install command only prints the pending dsh plugin command by default; add --execute to actually call the local dsh.
The repository requires Node.js 22 or higher.
Daily automatic synchronization, changes are committed back to main¶
The cron schedule for the GitHub Actions workflow sync plugins is 17 1 * * *, which corresponds to 09:17 Beijing time daily. The process is npm run sync → npm run check. If there are changes to README.md, README.en.md, catalog/plugins.json, or catalog/repositories.json, a commit titled “Automatically update plugin catalog” will be pushed to main. You can also run it manually on the Actions page.
Update the catalog locally:
npm run sync
npm run check
package.json also includes build, dev, and deploy scripts. The site is deployed using Cloudflare Workers (wrangler), with bound domains dsh-plugins.org and www.dsh-plugins.org.
Installation and Activation¶
The install command given on the community plugin catalog page is:
dsh plugin add github:lwmxiaobei/dsh-plugins
For reproducible installs, the catalog page recommends pinning a commit hash:
dsh plugin add github:lwmxiaobei/dsh-plugins#commit
Replace commit with the specific hash. Plugins run with the permissions of the current dsh process, and may execute code during installation; you should inspect the source code repository and license before installing.
As mentioned earlier, this repository itself does not have dsh.bundle.patch. If your only goal is to browse the catalog or copy others’ install commands, you do not need to install it into dsh first—just open dsh-plugins.org, or clone it and use the CLI as shown below.
Clone and view the local catalog:
git clone https://github.com/lwmxiaobei/dsh-plugins.git
cd dsh-plugins
npm install
npm run list
The engines.node requirement is >=22.
Typical Usage Examples¶
Find plugins on the website and copy install commands¶
Follow the site’s instructions, with the steps being:
1. Search by name, function, package name, or repository author, or narrow the scope by language or license.
2. Open the detail page and verify the repository, current package version, license, last update time, and catalog validation snapshot.
3. Copy the install command, execute it in the terminal running DeepSeek Harness, then perform configuration according to the upstream documentation.
The command example from the site list (the first entry on the homepage when viewed) is:
dsh plugin --profile web add github:liustack/modlens
This is an install specification assembled by the catalog based on the upstream repository; it actually installs the liustack/modlens plugin, not dsh-plugins itself.
Search and view details using the command line¶
The example given in the README:
npm run list
node bin/dsh-plugins.mjs search vision
node bin/dsh-plugins.mjs info Anionex/dsh-vision-toolkit
info will print the repository, package name, version, description, license, language, catalog validation commit, upstream address, and install specification.
Preview the install command first, then execute after confirmation¶
node bin/dsh-plugins.mjs install Anionex/dsh-vision-toolkit --profile web
This only previews the command by default. After confirming the upstream code and license:
node bin/dsh-plugins.mjs install Anionex/dsh-vision-toolkit --profile web --execute
The CLI will call:
dsh plugin --profile web add github:Anionex/dsh-vision-toolkit
If the dsh command is not available locally, the script will prompt you to install DeepSeek Harness first. If --profile is not specified, the CLI defaults to the web profile.
Get your plugin included in the catalog¶
The site FAQ and repository README are consistent: add the dsh-plugin topic to your public GitHub repository, and ensure the plugin manifest is complete (the root package.json declares dsh.bundle.patch, and the patch file exists). It will be rediscovered and validated during the next catalog synchronization; you can also open an issue in the catalog repository.
Applicable Scenarios and Notes¶
This is suitable for the following situations:
- You are new to DeepSeek Harness and want to browse community plugins by keyword, language, or license
- You need a list with basic bundle validation, instead of treating all repositories on the GitHub topic page as installable plugins
- You want to copy install commands that follow the upstream default branch, or preview locally before deciding whether to install
- You need a machine-readable catalog/plugins.json, or want to see why a certain repository was not included
Please note the following when using it:
1. Inclusion does not equal security audit. Both the README and the site state: inclusion does not mean official endorsement, security audit, or runtime compatibility. The catalog only validates public metadata and basic plugin structure. Before installing third-party plugins, you should inspect the upstream source code, permissions, dependencies, and license.
2. Plugins run with the permissions of the current dsh process. The catalog page also reminds users that code may be executed during installation. Do not install plugins from untrusted sources; for reproducible environments, pin a commit for dsh plugin add.
3. Install commands default to tracking the latest commit. The site clearly states that commands do not include a commit hash, and will fetch the latest version of the upstream default branch at runtime. The commit shown on the detail page is only the catalog validation snapshot.
4. NOASSERTION is not a permissive license. The repository notes that this means the GitHub API did not detect an explicit license, and you should not assume you have the right to copy, modify, or distribute the code by default.
5. This repository is not a runtime plugin marketplace UI. It does not bundle third-party plugin source code into its own package. If you want a visual marketplace in the Web GUI, you need to look for other marketplace plugins that declare dsh.bundle.patch; this project provides a navigation catalog and install commands instead.
6. The community catalog is independent of the official repository. The DeepSeek Harness official repository can add the dsh-plugin topic to plugins to help them be discovered, but catalog sites like dsh-plugins.org and deepseek-harness-plugin.com are all community-maintained, and should not be presented as official app stores.
Summary¶
dsh-plugins compiles repositories on GitHub with the dsh-plugin topic that pass the basic bundle manifest check into a searchable, filterable, bilingual navigation catalog, complete with the latest version install commands and a command-line install entry that only previews by default. For people choosing plugins for DeepSeek Harness, it is more like an automatically updated index, rather than another plugin that adds capabilities to the process.
Catalog page: https://deepseek-harness-plugin.com/zh-CN/plugins/dsh-plugins/
GitHub: https://github.com/lwmxiaobei/dsh-plugins
Website: https://dsh-plugins.org