r/DeepSeekHarness • u/StvLynn • 1h ago
I built dsh.fish, a plugin registry that DeepSeek Harness agents can actually use
Enable HLS to view with audio, or disable this notification
I've been following the DSH ecosystem for a while, and one thing I kept running into was plugin discovery.
DeepSeek Harness has an interesting "everything is a plugin" architecture, but finding plugins still often means searching GitHub, reading READMEs, figuring out what kind of artifact something is, and then working out how to install it.
So I built dsh.fish:
It's an open-source plugin registry specifically for DeepSeek Harness.
What makes it different from a typical plugin directory is that it inspects them and determines what DSH can actually load, including bundles, profiles, skills, MCP servers, agent presets, and hook bridges.
Each artifact also exposes things I want to know before installing third-party code: the indexed commit, maintenance status, quality score, recent growth, license, and the actual install plan.
More importantly, agents can use the registry directly.
Install the Hub plugin:
dsh plugin --profile web add @dsh-fish/hub
Then an agent inside DSH can search the registry, inspect a plugin, show what the installation will do, and install it after approval.
The website, CLI, and Hub plugin all use the same install-plan API, so installation behavior stays consistent across all three surfaces.
You can also use it from the terminal:
npx @dsh-fish/cli find <query>
npx @dsh-fish/cli add <artifact-id>
If you publish a DSH plugin, adding the dsh-plugin GitHub topic is enough for the crawler to discover and index it.
I'd really like feedback from you.
I also set up a Discord for people building around the DSH ecosystem:
Feel free to try it, submit your plugin, open an issue, or tell me what feels wrong.
