awesome-dsh-plugins

A spam-filtered, open-data registry of DeepSeek Harness (dsh) plugins, bundles, and skills — 20,769 entries from 12,181 authors across 17 functional areas, every one carrying the file its install path was proven in and the dsh version it was checked against.

Browse the reef — the same registry as a filterable, sortable gallery.

Most awesome lists are prose. This one is data: data/plugins.json is the source of truth, this README is rendered from it. Build on the JSON directly:

curl -s https://dsh.works/awesome-dsh-plugins/plugins.json                 # every entry
curl -s https://dsh.works/awesome-dsh-plugins/stats.json                   # just the counts, ~150 bytes

Each entry carries two orthogonal dimensions: category is the form factor (bundle, plugin, skill, theme, tool — what dsh docs call things) and tags is the functional area (what it actually does). stars is the linked repo’s GitHub count (refreshed by scripts/stars.mjs, display signal only), and featured marks a hand-curated editor’s pick.

Use this registry in dsh’s Discover tab

dsh 0.2.1 and later can browse a plugin market from one JSON index at a URL you add. The feature is experimental. This registry publishes an index built by scripts/market.mjs from every entry with a verified npm name whose published versions declare dsh.bundle; git-only entries are not in it yet.

1. Open Plugins, select More beside Experimental plugins, and switch on Custom plugin markets.
2. Select the Discover tab that appears, choose Add index source, and enter:

https://dsh.works/awesome-dsh-plugins/market/index.json

Use that address exactly: dsh refuses redirects, and the dshworks.github.io address redirects to it. Install opens a confirmation first, and dsh runs its own compatibility checks before anything is installed.

Why a filtered registry

DeepSeek delegates the ecosystem to the community: no first-party marketplace, discovery happens on the dsh-plugin GitHub topic. On launch day that topic held 431 repositories. As of 2026-10-20 it holds 21,187, template spam and topic-riders included. A raw topic feed is not a registry; the filter is the value this repo adds.

How much filtering that is, measured on 2026-10-20: 24,435 repositories carry a dsh discovery topic and 22,576 of them — 92% — have been opened, read, and decided. 3,172 were rejected, 2,707 of those for having no install path at any depth: no dsh manifest in package.json, no dsh dependency, no SKILL.md. They carry the topic and nothing else. Every rejection is published with its reason and a recheck date in data/rejected.json.

That is the number worth comparing. A topic count says how many people typed a tag. 22,576 of 24,435 says how many repositories somebody actually opened.

On 2026-08-20 that percentage fell, and it fell because the denominator got honest. Until then “carries a dsh discovery topic” quietly meant “carries one of the five dsh-* topics we sweep”, so every author who spelled the project out instead of abbreviating it was invisible to us while we published a coverage figure that read as though they were not there. Measured that day, in repositories carrying none of the original five: topic:deepseek-harness held 892, topic:dsh 163, topic:deepseek-harness-plugin 3 — 1,058 repositories, about 13% of the real universe, that a 99% claim had silently excluded. All of them are swept now. The percentage a wider net produces is lower and means more; a coverage number you can raise by narrowing what you count is not a coverage number.

Search is still not the whole ecosystem. A plugin whose author tagged nothing, published nothing to npm, and used no conventional layout is unreachable by any query — yjh051108/dsh-routing-suite had 6,415 stars and zero topics the day it was seeded. data/seeds.json is the hand-fed lane for those, and it grants nothing: a seed queues at the back like every other find and still has to prove an install path. If that is your repo, open an issue.

If you prefer a curated prose list, AdamPlatin123/awesome-dsh-plugins does that well, with daily compatibility tracking. This repo is the machine-readable complement, not a replacement.

Why “verified against” is a schema field

dsh is a developer preview and the team promises compatibility-breaking changes. Example: the .dsh-plugin manifest format was deleted on 2026-08-09 with no migration path, silently stranding every tutorial written against it. A compatibility claim without a version and a date rots, so the schema records both (verifiedAgainst, lastVerified) and stale entries get re-checked or flagged.

A version and a date still only say when somebody looked. evidence says where, as path#key:

"evidence": "package.json#dsh.bundle"
"evidence": "packages/theme/package.json#dependencies.@deepseek-ai/dsh-base"
"evidence": "skills/reviewer/SKILL.md#frontmatter"

Open the file and check. scripts/validate.mjs refuses a verified row that cannot cite one, so the status cannot quietly become decoration — which it had, on 2,751 rows, before this field existed.

And why npm is checked the same way

npm is the only field in an entry that is an instruction: dsh.works renders it as dsh plugin --profile web add , this README links it, and the spam gate accepts “a published npm package” as an install path. A reader can run it. So it gets the same treatment as evidence, and on 2026-08-21 it turned out not to have had it.

Of 582 names on that morning, 298 named a package registry.npmjs.org has never served — every one written on 2026-08-14, by a pass that read name out of the repo’s own package.json. That is the name an author would publish under, not evidence they did. On the site those 298 also replaced the git-install security warning with the sentence “Published to npm as”, so the wrong ones were quieter than the missing ones.

Fixing that surfaced the worse half. The names that did resolve had been checked against npm’s catalogue and not against ownership: dsh-tool-git resolves, so the field stayed — it resolves to lxj808624/dsh-tool-git, and it was sitting on Huasfan/dsh-tool-git. 26 pairs of entries claimed the same package as each other, and in 25 of them the wrong claimant was the 2026-08-14 row. Following one installed a different author’s code under the name of the repo you were reading about, which is a worse outcome than a 404.

A name is kept now only when the published package’s own repository.url names the repo back, or — for the packages that state no repository at all — when the repo’s package.json declares that exact name, so two independent files agree. npm run npm-check re-asks in both directions on a schedule; a name that stops resolving is parked in data/unpublished.json with the reason, a parked name that starts resolving is restored, and a name that merely times out changes nothing. Re-adding a parked name by hand fails validate.

The same pass answered the opposite question. Reading every entry’s manifest and asking npm about the name it declares adopted 1,741 packages the registry had found but never claimed — and refused 1,462 more whose name belongs to someone else, which is a third of everything it looked at.

Contents

• Editor’s picks
• Plugins by area
  • Web UI
  • Terminals & desktop
  • Tools & capabilities
  • Vision
  • Agents & orchestration
  • Memory & sessions
  • Models & providers
  • Interop & migration
  • Channels & remote
  • Notifications
  • Usage & cost
  • Observability & evidence
  • Safety & approvals
  • Plugin managers & stores
  • Developer tools
  • Knowledge & research
  • Fun
• Bundles
• Skills
• Themes
• Tools
• Add your plugin

Editor’s picks

Hand-curated, sparing, and revisited as the ecosystem moves; the ⭐ mark in the tables below means the same thing. Stars are the linked repo’s count, which for monorepo entries is the whole repo, not the plugin.

• dsh-web-ui — Plugin and skin collection for the dsh Web UI: task board, git graph, right-side panel, remote mobile UI, live token stats, and a skin center that routes around the theme-persistence gap 9123 ★ · ui
• modlens — Vision plugin for text-only models: image understanding bridged into the harness via a dsh.bundle patch layer, shipping a modlens skill alongside 4362 ★ · vision
• dsh-better-sidebar — Full sidebar workbench with file rendering/editing, terminal, Git, and subagents; third-party extensions can register new tabs 4356 ★ · ui
• dsh-browser — Chrome sidebar plugin that lets dsh operate the browser directly, without vision. 863 ★ · capabilities
• dsh-mnemon — Local-first three-tier memory for dsh: runtime memory, searchable documents, and supervised memory spaces. 604 ★ · memory
• whale-girl — Desktop-pet companion for the web GUI (QQ-pet style): draggable, feedable, levels up with session activity; migrated from the removed .dsh-plugin format to dsh.bundle 369 ★ · fun
• dsh-turn-rewind — Rewind conversation and workspace state to a previous turn, backed by a persistent change ledger 136 ★ · memory
• dsh-usage-stats — Beautiful token analytics for DeepSeek Harness — trends, activity heatmaps, model breakdowns, and data exports. 11 ★ · usage

Plugins by area

19968 Cordis plugins activated through patch rows in a bundle or profile, grouped by what they do. Data updated 2026-10-20.

Each area shows its 25 most-starred entries and links to the complete list in lists/. GitHub stops rendering a markdown file partway through once it passes about half a megabyte — silently, mid-row — so the full tables live in files small enough to survive that. Nothing is dropped: data/plugins.json and the gallery always hold everything.

Web UI

Panels, composer upgrades, navigation, layout, mobile.

Showing the 25 most-starred of 1608. all 1608 → · gallery · JSON

Terminals & desktop

TUIs, desktop shells, headless runners.

Showing the 25 most-starred of 673. all 673 → · gallery · JSON

Tools & capabilities

New things the model can do: search, browser, files, databases, devices, media.

Showing the 25 most-starred of 5330. all 5330 → · gallery · JSON

Vision

Image understanding for text-only models.

Showing the 25 most-starred of 656. all 656 → · gallery · JSON

Agents & orchestration

Subagents, workflows, cross-session coordination.

Showing the 25 most-starred of 1754. all 1754 → · gallery · JSON

Memory & sessions

Memory systems, context management, session search/rewind/export.

Showing the 25 most-starred of 2734. all 2734 → · gallery · JSON

Models & providers

Providers, routing, fallbacks, subscription adapters.

Showing the 25 most-starred of 1383. all 1383 → · gallery · JSON

Interop & migration

Bridges to and from Claude Code, Codex, and other harnesses.

Showing the 25 most-starred of 642. all 642 → · gallery · JSON

Channels & remote

IM bridges and remote control: Feishu, Telegram, WeCom, DingTalk.

Showing the 25 most-starred of 382. all 382 → · gallery · JSON

Notifications

Alerting the human: desktop, sound, even a phone call.

Showing the 25 most-starred of 379. all 379 → · gallery · JSON

Usage & cost

Token accounting, billing, balance, quota.

Showing the 25 most-starred of 1230. all 1230 → · gallery · JSON

Observability & evidence

Diagnostics, logs, audits, content-addressed proofs.

Showing the 25 most-starred of 315. all 315 → · gallery · JSON

Safety & approvals

Permission tiers, gates, redaction, protection.

Showing the 25 most-starred of 671. all 671 → · gallery · JSON

Plugin managers & stores

In-UI stores, installers, skill managers.

Showing the 25 most-starred of 627. all 627 → · gallery · JSON

Developer tools

Building, testing, and publishing plugins.

Showing the 25 most-starred of 270. all 270 → · gallery · JSON

Knowledge & research

Research workbenches, RAG, learning modes.

Showing the 25 most-starred of 679. all 679 → · gallery · JSON

Fun

Games, pets, memes, ambience. The reef has coral.

Showing the 25 most-starred of 635. all 635 → · gallery · JSON

Bundles

npm packages with a dsh.bundle manifest: composition layers a profile boots from.

Showing the 25 most-starred of 102. all 102 → · gallery · JSON

Skills

Anthropic-format SKILL.md units; dsh discovers them from its skill roots (no nested discovery, kebab-case names only).

Showing the 25 most-starred of 694. all 694 → · gallery · JSON

Themes

UI skins. The dedicated registry is awesome-dsh-themes; only themes that also ship plugin machinery live here.

Tools

Developer tooling around dsh.

Add your plugin

Open a PR against data/plugins.json only; the README is regenerated. See CONTRIBUTING.md. The spam gate in short: a real install path (a dsh.bundle manifest, a published npm package, or a SKILL.md layout dsh discovers), not a renamed template fork, and it loads against the dsh version you claim. Pick one or two tags from the schema’s list so your entry lands in the right area.

A scheduled workflow also sweeps every dsh discovery topic, npm, and GitHub code search; new finds queue in data/candidates.json on a single reused triage PR and never enter the registry without review. Rejected candidates are recorded with one-line reasons in data/rejected.json. Rejections of judgment (“this is a curated list”) are permanent; rejections of fact (“no install path on the day we looked”) carry a recheckAfter date and are swept again once it passes, so shipping a manifest late is not a life sentence.

Already listed?

Most entries here arrived by sweep, not by PR, so plenty of authors are in the registry without knowing it. Search this README, or:

curl -s https://dsh.works/awesome-dsh-plugins/plugins.json | jq '.plugins[] | select(.repo=="you/your-plugin")'

If the row is wrong — bad description, wrong tags, a version you have since moved past — the fix is a PR against the data file, and it is the fastest way to correct it.

If you want to say so in your own README, this badge is static — it points here and needs no upkeep:

[![listed on dsh.works](https://img.shields.io/badge/listed_on-dsh.works-00c2e9?labelColor=0d0d0d)](https://dsh.works/awesome-dsh-plugins/)

It is a link, not a certification: it means your plugin is in an open-data registry that publishes its rejections too, and nothing more.

Field notes

Verified dsh traps, skill discovery rules, and hook-bridge limits live in howto-dsh.

License

MIT. Not affiliated with DeepSeek; the harness README calls itself “an idea, an official showcase, and a source of inspiration”, and the ecosystem belongs to the community.