The Curated Plugin List for DeepSeek Harness, Installable in One Command

You've found a plugin you want to try, but now you're juggling installation instructions, version compatibility, and a dozen open browser tabs. DeepSeek Harness (DSH) makes everything a plugin—models, tools, sandboxes, UI, even the agent loop—which means the ecosystem can grow fast, but discovery gets messy. Awesome DSH Plugin is a curated list that fixes that, and it's installable via dsh plugin add.

What It Does

At its core, this is an Awesome-style list: a curated collection of community plugins for DeepSeek Harness, DeepSeek's open-source agent harness. DSH is a runnable coding agent (Web and headless) built on a framework where everything is a plugin. Plugins can extend the official coding agent, swap out core parts, or assemble something entirely different.

The list has a practical constraint that keeps it useful: an entry is added only when the plugin installs with dsh plugin add (each declares a dsh.bundle manifest), does what its one-line description says, sits in the right category, and is maintained. Every submission is checked against its own source before merging—so if a description claims "46 tools," someone actually verifies it.

Beyond the list itself, there's a second layer worth knowing about. On dsh 0.2.1+, the list doubles as a plugin market index. You open Plugins → Discover → Index sources and add a jsDelivr-hosted index.json. That's the same list in format-1 index form, served from npm so it loads quickly everywhere—dsh gives a source 15 seconds to respond, and the GitHub Pages copies can exceed that from some networks. The Discover tab and the plugin_market agent tool then search the same entries. The index covers plugins published on npm with a known version; GitHub-only entries still install with the command beside them.

Why It's Cool

• The install path is the filter. Because listing requires a working dsh plugin add and a declared manifest, you're not wading through half-abandoned experiments. The list's criteria do the boring quality control for you.

• The index format is a clever bit of engineering. Serving the catalog from npm via jsDelivr instead of GitHub Pages is a small decision with real consequences—it's about latency budgets, and it means the in-app Discover tab actually feels usable rather than timing out on slow networks.

• It's client-agnostic by design. A plugin is listed because it follows the official protocol, not because it adapts to one particular client. The README points to several desktop clients (dsh-desktop, deepseek-harness-desktop from both hairyf and anywhere-labs) that ship the dsh-market plugin browser built in, so everything on the list is one click away.

• There are multiple ways to browse. You can use the dsh-market plugin market inside DSH with one-click install and upgrade plus one-click theme switching, or if you prefer chat, dsh-find-plugin lets your agent find plugins for you. Different entry points, same catalog.

• It's honest about risk. The README carries a clear warning: installing a plugin runs third-party code with your own permissions—it can read your files, use your credentials, and reach the network. Tool approvals don't sandbox plugin code, and being on the list is not a security review. That's the kind of disclaimer more curated lists should include.

How to Try It

1. Start with the repository itself: awesome-dsh-plugin. Browse the categories and find something that fits your workflow.

2. Install a plugin the standard way—each entry lists its command, and they follow the pattern:

   dsh plugin add <plugin-name>
   

3. If you want the in-app market experience (optional but recommended), install dsh-market:

   dsh plugin --profile web add dshmarket
   

4. To wire up the catalog as a Discover index on dsh 0.2.1+, open Plugins → Discover → Index sources and add:

   https://cdn.jsdelivr.net/npm/dsh-plugin-catalog/index.json
   

5. Prefer asking your agent? Add the finder plugin:

   dsh plugin --profile web add dsh-find-plugin
   

Before installing anything unfamiliar, check the source—especially on machines that hold credentials or keys.

Final Thoughts

This is a list, not a framework, and its value depends entirely on the quality of what gets merged—which is exactly why the source-checking policy matters. If you're running DeepSeek Harness and want to extend it without spelunking through GitHub search, this is the sensible starting point. The dual role as an npm-served market index is a nice touch that makes it more than a static README. Give it a look, and if you've built something that installs cleanly and does what it says, the project welcomes PRs.

Follow @githubprojects for more developer tools and open source projects.