Preface¶

DeepSeek Harness (referred to as DSH, with the command line tool dsh) treats models, tools, sessions, sandboxes, and interfaces as plugins, with the official repository positioning itself as “everything is a plugin”. It is currently in developer preview, and compatibility may change at any time. The official entry point is npx @deepseek-ai/dsh web, and the source code repository can be found at https://github.com/deepseek-ai/deepseek-harness.

After going open source, the community repository has grown rapidly. The dsh-plugin topic on GitHub, various awesome lists, and independent plugin sites are all collecting plugins, but the standards are inconsistent: some include adjacent tools, while others only accept bundles with cordis.patch.yml. For users, the pain points are concrete: they want to filter “plugins that can truly be installed into dsh” by category, or find categories like visualization, usage statistics, and sandboxes by star count. GitHub search can only cover topics or keywords at a time, and static READMEs quickly become outdated.

Blue-Whale-Harness was built exactly for this purpose. It is maintained by leenkcool, and the community plugin directory categorizes it under “Development and Runtime”. The repository’s own tagline is: “Index all DeepSeek Harness (DSH) plugins generated from the open source community”. Two things need to be clarified first: https://deepseek-harness-plugin.com is an independent community site and has no official affiliation with DeepSeek / Fangfu; Blue-Whale-Harness itself is primarily an index and static master list, not a Cordis bundle that inserts tools or UIs into the dsh process.

What is Blue-Whale-Harness¶

The repository address is https://github.com/leenkcool/Blue-Whale-Harness, with the GitHub description DeepSeek-Harness-Plugins, primarily marked with HTML as the main language, and licensed under Apache-2.0. The repository was created on 2026-08-13, and as of the time this document was checked, it had 125 GitHub stars (121 when crawled by the community directory page), with 46 forks. The directory page was added on 2026-08-17.

It solves the problem of discovery, rather than extending the capabilities of a single conversation. When the README was auto-generated on 2026-08-17, the snapshot showed: a total of 1818 repositories, of which 1688 were marked as “real DSH plugins”. The online master list is deployed at https://leenkcool.github.io, supporting Chinese and English search, category filtering, and sorting by STAR and other fields.

There is no package.json or cordis.patch.yml in the repository root directory. According to the official packaging documentation, a bundle that can truly activate the configuration layer needs to declare dsh.bundle in package.json; even if a package without this declaration is added to the profile via dsh plugin add, it will only be a regular dependency and a warning will be printed. Therefore, the daily usage is to open the master list or README, navigate to the target repository, and then install the plugin itself.

Core Features and Highlights¶

Based on the README, catalog/ scripts, and the online master list page, the verified capabilities are as follows.

1. Categorized plugin list. The README groups repositories by category, sorted in descending order of STAR within each group, with columns including the repository link, Chinese and English intent, star count, main language, and whether it is a “real DSH plugin”. The number of categories in the 2026-08-17 snapshot was:

The README also provides the total star count for each category. The total can be significantly inflated by a few high-star repositories, so it should not be directly interpreted as the “total star count of the DSH plugin ecosystem”.

2. “Real DSH” heuristic marking. catalog/analyze.mjs checks whether a local clone has cordis.patch.yml, whether it depends on @deepseek-ai/ or Cordis, the package.json keywords, and whether the README mentions DeepSeek Harness / dsh-plugin. If the conditions are met, isDshPlugin is set to true. This is a programmatic heuristic, not an official certification, nor does it equal a security audit.

3. Chinese and English intent fields. The analysis script first uses the Chinese and English descriptions from the repository itself; if one side is missing, it uses Google gtx / MyMemory for translation and caches the result; if neither side has usable descriptions, it falls back to a code analysis sentence based on package.json and file fingerprints. Two columns, “Intent (Chinese)” and Intent(EN), can be seen on the master list.

4. Searchable static site. catalog/generate.mjs generates index.html, plugins.zh.html, plugins.en.html, and plugins.csv. The online entry points include:
   - Master list: https://leenkcool.github.io
   - Chinese version: https://leenkcool.github.io/plugins.zh.html
   - English version: https://leenkcool.github.io/plugins.en.html
   - CSV: https://leenkcool.github.io/plugins.csv

The page provides filters for “all categories / only real DSH / only non-DSH”, and sorting by STAR, FORK, creation time, update time, and repository name. The website artifacts are deployed to https://github.com/leenkcool/leenkcool.github.io.

5. Machine-readable data. The repos.json, repos.txt, and catalog/plugins.csv in the root directory can be directly consumed by scripts. The fields include repository name, category, language, license, star count, Chinese and English descriptions, etc.

6. Post-clone risk scanning script. catalog/risk-scan.mjs performs static feature scanning on cloned repositories, such as webshell patterns, obfuscated eval, credential collection, exfiltration URLs, etc., and writes the results to catalog/risk-scan.json. This is a scanning pipeline on the maintainer’s side, and the master list page does not display scan results as user-facing security ratings; inclusion in the list does not equal endorsement of security.

Installation and Activation¶

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

dsh plugin add github:leenkcool/Blue-Whale-Harness

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

dsh plugin add github:leenkcool/Blue-Whale-Harness#<commit>

The directory page also states that the plugin runs with the permissions of the current dsh process, and may execute code during installation; please check the source code repository and license before installing. The official documentation also reminds that when installing from Git, pnpm may require explicit authorization of the prepare build script, and the authorized code will execute outside the Agent sandbox.

For this repository, a more secure usage method is to treat it as a directory to browse, rather than expecting a market interface to appear immediately after installation:

git clone https://github.com/leenkcool/Blue-Whale-Harness.git
cd Blue-Whale-Harness

Then directly open the README, or point your browser to https://leenkcool.github.io. After finding the target plugin, install it according to the plugin’s own instructions, for example:

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

After installation, to confirm whether the configuration layer is effective, the official documentation suggests checking with:

dsh --profile web --dump-config

Typical Usage¶

1. Finding plugins in the online master list¶

Open https://leenkcool.github.io, and select as needed:
- Category: e.g., llm, tools, sandbox, ui
- Scope: Only real DSH or Only non-DSH
- Sort: By STAR or by update time

Click the repository name to jump to the original GitHub project. Confirm the README, license, and dsh.bundle / cordis.patch.yml before executing the dsh plugin add for that project.

2. Using CSV for local filtering¶

If you prefer spreadsheet tools, you can download:

https://leenkcool.github.io/plugins.csv

Use spreadsheet software to filter by category, star count, or the “real DSH” column. The CSV comes from the same generation script as the HTML master list.

3. Starting from the README category table¶

The “Plugin List” section of the README is sorted by category, with each group sorted in descending order of STAR. For example, to find vision-related capabilities, first look for entries with vision / image recognition descriptions in the llm group; to find sandboxes or automatic approval, directly navigate to the sandbox section. Clicking the repository name will also jump to the original project.

4. How maintainers regenerate the master list¶

The commands given in the “How to Generate / Update” section of the README are:

node catalog/analyze.mjs     # Collect repository metadata + intent (translated via HY3)
node catalog/merge.mjs       # Apply manual translations
node catalog/generate.mjs    # Generate website artifacts such as catalog/index.html
node catalog/build-readme.mjs # Regenerate this README

There are also clone.mjs (clone repositories) and the aforementioned risk-scan.mjs in the catalog/ directory. Regular users do not need to run this pipeline.

Applicable Scenarios and Notes¶

Suitable for:
- New DSH users who want to browse community plugins by category instead of relying solely on GitHub topic searches.
- Users who need a Chinese-English对照 list that can be sorted by star count, or want to connect the CSV to their own scripts.
- Plugin authors who want to compare against the “real DSH” heuristic to check if their repository has cordis.patch.yml, keywords, and README signals.

Things to note:
- The community directory and this master list are not official app stores. Inclusion, star count, and “real DSH” markers do not equal quality assurance or security audits.
- The index itself is collected and organized under Apache-2.0; each plugin’s copyright belongs to its original author, and the license shall prevail for the target repository.
- “Real DSH” is a file and dependency heuristic, which may mark adjacent projects that mention DSH as yes, and may also miss real plugins with atypical structures. Always read the target repository before installing.
- Plugins run with the permissions of the current dsh process. Check the source code and license before installing, and try to pin the commit; do not execute dsh plugin add solely based on the one-sentence intent in the master list.
- DeepSeek Harness is still in developer preview, and the official README notes that there will be breaking compatibility changes. Plugins that work today may need to be updated along with the main project in the future.

Summary¶

Blue-Whale-Harness aggregates DSH-related repositories scattered across GitHub into a searchable master list: with categories, Chinese and English intents, “real DSH” markers, star count sorting, and three export channels: CSV, static site. It does not replace the official Harness, nor does it add new tools at runtime; its value is turning “where to find plugins” from topic searches into a filterable directory.

Community directory page: https://deepseek-harness-plugin.com/zh-CN/plugins/blue-whale-harness/

GitHub: https://github.com/leenkcool/Blue-Whale-Harness

Online master list: https://leenkcool.github.io