Preface

DeepSeek Harness (dsh) treats models, tools, skills, sessions, sandboxes, storage, loops, scheduling, and UI as replaceable plugins, officially described as “everything is a plugin”. On August 13, 2026, DeepSeek open-sourced this Cordis-based agent runtime as a developer preview, and the community repository has grown rapidly. There are now many projects tagged with the dsh-plugin topic on GitHub, including desktop wrappers, skins, visual tools, memory plugins, and various marketplaces. It is not easy to match the capability seams in the official introduction when flipping through pages by stars or release time.

Awesome-DeepSeek-Harness-Plugins emerged against this background as a bilingual curated catalog. It does not provide new tool calls, but organizes public, DSH-facing plugins and extensions according to the official classification, and attaches repository addresses, current star counts, and independently verified reference web pages.

What is this

Awesome-DeepSeek-Harness-Plugins is maintained by Zhiyuan-Fan and licensed under the MIT license. The community site DeepSeek Harness Plugin Library lists it under the “Skills” category, with an inclusion date of 2026-08-15. This site is an independent community directory, not officially affiliated with DeepSeek / Hujiang, and should not be treated as an official app store.

The GitHub repository was created on 2026-08-13. As of 2026-08-17, the GitHub API shows 102 stars and 18 forks, with the default branch being main. There are currently only three files in the repository root: LICENSE, README.md, and README.zh-CN.md, with no package.json, plugin manifest, or SKILL.md. Based on its current state, it is first and foremost an Awesome List: the daily usage is to read the README and then install the specific plugins listed, rather than expecting to add a set of callable skills by installing it into dsh.

How the catalog is organized

The Chinese and English READMEs are maintained synchronously, and the classification system directly follows the capability seams in the official Harness introduction, rather than mixing entries by stars or release time. The current categories are as follows:

  1. Models and Providers: Routing, fallback, OAuth, usage statistics, and model metadata completion.
  2. Tools and Skills: Vision, search, file references, research workspaces, code review skills, etc.
  3. Sessions and Storage: Long-term memory, fallback, session import, context compression.
  4. Loops and Scheduling: Multi-agent teams, workflows, scheduled reruns, conditional wake-up.
  5. Runtime and Sandbox: Windows / SSH / containers, approval gates, standalone distributions.
  6. UI and Clients: Web skins, desktop pets, TUI, desktop and mobile wrappers.
  7. Integrations: Browsers, QQ / Feishu, MCP, ACP, CI.
  8. Development and Operations: Plugin marketplaces, usage statistics, security audits, scaffolding.

Each entry includes a standard GitHub repository, a one-sentence description, the current Stars badge, and a “Reference Webpage” column. The maintainer states that the references have been independently verified; many entries currently show “No verified reference webpage available”, and the list does not pretend that every entry has external documentation backing.

Within the same category, entries are sorted first by GitHub Stars, then by the number of verified reference webpages. The inclusion criteria are stated at the beginning of the README: public, practical, actively maintained, and explicitly targeted at DSH. The README also reminds users to inspect the plugin code and permissions before installation.

As of the README pulled on 2026-08-17, there are approximately 294 community projects (plus the official Harness itself). The counts per category are uneven: UI and Clients has about 101 entries, Development and Operations has about 60, Tools and Skills has about 42, Integrations has about 32, and the remaining categories have even fewer entries. The UI category has a high degree of duplication for desktop clients, skins, and desktop pets, and the same product name may correspond to multiple repositories, such as several dsh-desktop instances and two dsh-ssh repositories. These numbers change with daily updates and should not be treated as a fixed inventory.

The maintenance methods are also documented in the repository: the list is checked daily by a local Codex scheduled task using public sources. There are two ways to contribute: submit a Pull Request directly, or add the dsh-plugin topic to your repository so that the maintenance task can discover it.

Installation and Activation

The installation command given on the community directory page, to be run in the DeepSeek Harness terminal, is as follows:

dsh plugin add github:Zhiyuan-Fan/Awesome-DeepSeek-Harness-Plugins

For reproducible installations, the directory page recommends pinning the commit hash:

dsh plugin add github:Zhiyuan-Fan/Awesome-DeepSeek-Harness-Plugins#commit

Replace commit at the end with the actual hash. The plugin runs 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.

It is important to distinguish two things. The directory page lists this repository as a skill plugin that can be installed via dsh plugin add, but the repository itself currently has no Cordis plugin entry point. Whether this command can install it as a runnable runtime plugin depends on the current git dependency resolution result of dsh, do not assume that it will add new tools or commands to the agent. If you only want to browse the catalog, you can directly open the README on GitHub without going through plugin installation.

Typical Usage

The more common usage is to treat this README as an index. The Chinese catalog is at:

https://github.com/Zhiyuan-Fan/Awesome-DeepSeek-Harness-Plugins/blob/main/README.zh-CN.md

You can also clone the repository locally and jump between categories using your editor:

git clone https://github.com/Zhiyuan-Fan/Awesome-DeepSeek-Harness-Plugins.git
cd Awesome-DeepSeek-Harness-Plugins

The local files are README.zh-CN.md (Chinese) and README.md (English). For example, to “add vision support to plain text models”, you can open the “Tools and Skills” category and look for entries like modlens, dsh-vision-toolkit, or dsh-vision-router in the descriptions. To “find a desktop client”, go to “UI and Clients” and note that the same product name may have multiple repositories. After reading the description, star count, and reference webpage, click into the target repository, verify the installation command, license, and source code, then install that plugin, not this catalog itself.

The catalog also includes discovery projects, such as dsh-find-plugins (search and install plugins by dsh-plugin topic) and dsh-market (in-app plugin marketplace). These solve the problem of “searching for plugins in a running dsh instance”, and complement this static README catalog rather than replacing it. After selecting a specific plugin, the installation command should follow its own README or catalog page, with the common format being dsh plugin add github:owner/repo.

Applicable Scenarios and Notes

This catalog is suitable for three groups of people: those new to DSH who need to browse community projects according to official capability seams; those who want to add vision, memory, TUI, or desktop shells to their agents, and do not want to rely solely on GitHub topic pages by chance; and authors who have released plugins and want them to be included in the bilingual catalog.

There are several boundaries to clarify when using it.

First, inclusion does not equal endorsement. The README itself states “please inspect the plugin code and permissions before installation”. Community plugins run with the permissions of the current dsh process, and may execute build scripts during installation, which are not within the Agent sandbox. Do not grant allowBuilds just based on star count or “included in the list”.

Second, it is not a runtime plugin marketplace. Projects like dsh-market and DSH-Plugins-Marketplace support searching, installing, and updating plugins in the web interface; Awesome-DeepSeek-Harness-Plugins provides a static list with categories and reference columns. GitHub topic pages, the community site deepseek-harness-plugin.com, and this README are all community indexes, and their authority is subject to the repository of each individual plugin.

Third, the quality of entries varies widely. A large number of projects still show “0 webpages / no verified reference webpage available”; some entries are marked as Archived; when multiple repositories share the same name, you need to compare the maintainer, recent pushes, and README before choosing, do not just go by the repository name.

Fourth, DeepSeek Harness is still in developer preview, and the official repository notes that there will be breaking changes. The list is updated daily, but it still cannot keep up with situations where a plugin suddenly changes its installation method or license. When installing a specific plugin, prioritize pinning the commit, and follow the instructions from that repository at the time.

Summary

Awesome-DeepSeek-Harness-Plugins gathers scattered DSH community projects on GitHub into a bilingual catalog according to official capability seams, and adds star counts and verified references. It solves the problem of “finding first before deciding which to install”, rather than adding new capabilities to the dsh process. Using the README as an index, inspecting the source code, license, and installation command after selecting a target is currently the most reliable way to use it.

  • Community directory page: https://deepseek-harness-plugin.com/zh-CN/plugins/awesome-deepseek-harness-plugins/
  • GitHub: https://github.com/Zhiyuan-Fan/Awesome-DeepSeek-Harness-Plugins
  • DeepSeek Harness official repository: https://github.com/deepseek-ai/deepseek-harness