Preface

DeepSeek Harness (referred to as dsh for short) is an open-source agent runtime developed by DeepSeek. Its core concept is “everything is a plugin”: models, tools, sessions, sandboxes, and interfaces can all be replaced via plugins without modifying the Harness source code. The official repository also has an agreement: community plugins tagged with the dsh-plugin topic on GitHub can be discovered by the ecosystem.

A very practical problem arises in actual use. There are already many plugins, with indexes on the community directory, curated list, and GitHub topic page respectively, but you are still in the Harness session: when you want to find capabilities such as “send WeChat when task completed”, “terminal TUI”, “git diff review”, you often have to switch out to search, then copy the installation command back. What dsh-find-plugin does is bring this step into the session — let the agent search on its own and bring back the results and installation commands.

This article introduces dsh-find-plugin maintained by awesome-dsh-plugin (do not confuse it with another similarly named dsh-find-plugins). The information is cross-checked against the plugin directory page, GitHub README / source code, npm package, and DeepSeek Harness official repository. The community plugin directory is an independent site and has no official affiliation with DeepSeek / HyperMind; do not treat it as an official app store.

What is it

dsh-find-plugin is a development and runtime plugin maintained by the GitHub organization awesome-dsh-plugin. It registers a tool find_dsh_plugin for the agent: it performs real-time retrieval of GitHub repositories tagged with the official dsh-plugin topic by keywords, sorts them by stars, and returns a one-sentence description, repository link, and directly executable dsh plugin add command.

The repository README compares it to /find-skills on skills.sh, only targeting DSH plugins instead. The license is MIT. The main language is TypeScript, and the npm package name is dsh-find-plugin. The version verified in this article is 0.3.6 (released on 2026-08-14). The star count of the GitHub repository read on 2026-08-17 is 40 (the directory page still showed 20 at that time, please refer to the real-time GitHub data). The plugin has been included in the “Development and Runtime” category of the community directory, with an inclusion date of 2026-08-14.

It solves a narrow problem: you can search for candidate plugins by capability description without leaving the current Harness session. It does not review the source code for you, nor does it implement the step of “checking if installed plugins are available” in its source code; the “check and verify installation” in the directory page’s introduction cannot be found in the find_dsh_plugin implementation of the current repository. If you ask the agent to install after searching, it will run the returned installation command — it is still installing third-party code.

Core Features

Combining the README and source code (src/index.ts, src/github.ts, src/registry.ts), the current capabilities can be summarized as follows.

  1. Real-time repository search by topic. The query will be assembled into the GitHub search keywords topic:dsh-plugin, using anonymous API without requiring you to configure a Token. The same query has a 5-minute in-memory cache. The source code comments note that unauthenticated searches allow approximately 10 requests per minute, and the cache is used to keep local tool calls within the rate limit. The tool timeout is 10 seconds, and the GitHub request timeout is 4 seconds.

  2. Re-sort by stars. Search results are sorted in descending order by stargazers_count. The default maximum return is 8 entries, with a limit cap of 20. Each entry includes the name, star count, description, repository URL, and an installation command in the format:

dsh plugin --profile web add github:owner/repo

  1. Curated list only modifies descriptions, not rankings. If a repository also appears in plugins.json of awesome-dsh-plugin, the manually written bilingual description in the list will replace the GitHub repository’s profile. The lang parameter selects the language (e.g. zh / en), with the default being en. If the curated list cannot be pulled, it will fall back to the snapshot from the repository, and if that fails, it will only use the GitHub description. Sorting is always done by stars and is not affected by the curated list.

  2. Called by the agent automatically in conversations. After installing and restarting dsh web, you do not need to remember the tool name. You can say what capability you want in natural language, and the agent will call find_dsh_plugin on its own when it judges that “the current Harness lacks this capability” or “the user is asking about plugins”.

The tool parameters are as follows (from the defineTool definition in the source code, not guesswork):
- query: Required. Keywords describing the capability, such as wechat notifications, TUI, cross-session memory.
- limit: Number of returned entries, default 8, maximum 20.
- lang: Curated entry description language, default en. For Chinese environments, you can have the agent use zh.

Installation and Activation

The installation command given on the community directory page is:

dsh plugin add github:awesome-dsh-plugin/dsh-find-plugin

The repository README and the awesome-dsh-plugin details page recommend using the npm pre-built package and explicitly specifying the web profile (which is consistent with the writing in DeepSeek Harness official documentation dsh plugin --profile <profile> add ...):

# npm package (pre-built, recommended by README)
dsh plugin --profile web add dsh-find-plugin

# Or install from GitHub
dsh plugin --profile web add github:awesome-dsh-plugin/dsh-find-plugin

For reproducible installations, pin the commit hash as instructed on the directory page, do not keep tracking the default branch of the repository:

dsh plugin add github:awesome-dsh-plugin/dsh-find-plugin#<commit>

A few notes during installation:
- The plugin runs with the permissions of the current dsh process, and may execute build scripts during installation. Please review the source code repository and license before installing.
- The README clearly states: after installation, you need to restart dsh web for the tool to appear in the current session.
- When installing TypeScript source code from GitHub, pnpm 10 and above may block the prepare / build script. The awesome-dsh-plugin details page notes: if allowBuilds is prompted during the first add, follow the prompt to add the package name to the profile’s pnpm-workspace.yaml and execute the command again. The npm pre-built package generally does not require this step, so the README marks it as the recommended path.
- This package declares dsh.bundle.patch pointing to ./cordis.patch.yml in package.json, and the patch will insert the line with id find-dsh-plugin into the plugin stack of the profile. The peer dependencies are @deepseek-ai/cordis and @deepseek-ai/dsh-tools.

Typical Usage

After installing and restarting, you can talk directly to the agent. The examples given in the README are as follows and can be used directly for testing:

Are there any terminal TUI plugins?
I want to receive WeChat notifications when tasks are completed, are there any plugins?
Find something that can do git diff review in DSH.

After the agent calls find_dsh_plugin, it will get text similar to the following (the format comes from the source code’s renderText, the specific entries change with real-time GitHub results, here only the structure is explained):

1. Plugin Name ★123 — One-sentence description
 https://github.com/owner/repo
 install: dsh plugin --profile web add github:owner/repo

Each entry comes with stars, description, repository link, and installation command. The README clearly states: you can ask the agent to execute one of the dsh plugin add commands next. If no results are found, the tool will prompt to use broader keywords or browse the curated list at https://awesome-dsh-plugin.com.

A fixed note will also be attached to the returned results: these are all third-party code, please review the source code and lock the commit before installing. This is not just a formality, it is consistent with the security prompts on the directory page and official documentation.

Applicable Scenarios and Notes

It is more suitable for these types of users: those who are already using dsh web, often need to add capabilities to the agent, but do not want to switch to the browser to flip through GitHub topics or the community directory every time. The search is most effective when the keywords correspond to the repository name or profile, such as TUI, notifications, diff, memory.

There are several boundaries to keep in mind when using it:
1. It searches GitHub topics, not an “officially certified store”. Any public repository tagged with dsh-plugin may appear. Plugins without the topic cannot be found. DeepSeek Harness itself only treats this topic as a discovery convention and does not endorse community plugins.
2. Curated descriptions and search scope are not the same thing. The awesome-dsh-plugin details page has a line that says “search this curated registry by keywords/categories”; comparing with the source code, the actual request is sent to GitHub repository search, and the curated plugins.json is only used to replace descriptions. Categories are not tool parameters. When writing this article, refer to the source code and README’s “How it works”.
3. Do not install the wrong plugin with the same name. There is also dsh-find-plugins in the community directory (maintained by Nagi-ovo, with installation and verification process). The one introduced in this article is awesome-dsh-plugin/dsh-find-plugin, and the installation command and repository address are different.
4. Anonymous API has rate limits and relies on network connectivity. No GitHub Token is configured. The cache is based on query strings, and changing keywords will result in a new request. If GitHub search fails, the tool will report an HTTP error and will not quietly fabricate results.
5. The security model is consistent with the official one. The directory page clearly states: plugins run with the permissions of the current dsh process and may execute code during installation. DeepSeek Harness official documentation also reminds: allowing build scripts is equivalent to allowing third-party code to be executed on the local machine during installation, and it is not in the agent sandbox. Only install sources you trust, and try to pin commits. The candidates searched by dsh-find-plugin itself also follow the same rule — it gives you the command, not a guarantee.

DeepSeek Harness is still in developer preview at present, and the official README clearly marks in uppercase that there may be breaking changes. The plugin’s tool API and profile installation method may change in the future, please check the current repository README before installing.

Summary

dsh-find-plugin brings the act of “finding repositories with the dsh-plugin topic on GitHub” into the Harness session: real-time search, sorting by stars, attaching installation commands, and using manually written bilingual descriptions when hitting the curated list. It does not replace your review of third-party code, it just saves one step of switching out to browse the directory.

Directory page: https://deepseek-harness-plugin.com/zh-CN/plugins/dsh-find-plugin/

GitHub: https://github.com/awesome-dsh-plugin/dsh-find-plugin

npm: https://www.npmjs.com/package/dsh-find-plugin