DeepSeek Harness plugins,one command away.

What it is — Builds inspectable, standalone interactive diagrams—architecture, workflow, sequence, data-flow, lifecycle—from a repo or a system write-up.

Who it is for — You are in a DeepSeek Harness session reviewing or handing off a system from a repo or a description, and you need a diagram the other person can open and explore. If architecture already has its own pipeline and the agent only patches code, skip it.

Watch out — It installed in a clean profile and was registered. It will run shell commands; know that before you add it.

The verdict — Keep it out of the profile unless turning repos into diagrams is a regular part of the week.

What it is — Wires unpaid model lanes, a localhost OpenAI-compatible gateway, named fallback chains, and an on-machine usage dashboard into DeepSeek Harness.

Who it is for — You are in DeepSeek Harness shipping code or running an agent with no API key, and you need DeepSeek V4.1 Flash or Kimi K3 on the selector—or the same models exposed on localhost for other clients. Skip it where policy allows only private or leased-line egress; the unpaid lanes talk to the OpenCode Zen and Kilo public gateways.

Watch out — Reachability is whatever your machine’s egress actually gets; geo-blocked ids land in a region-limited group, while 5xx, 429, and timeouts do not drop a model from the picker. Kilo’s free pool states prompts may be logged. Marked beta, listed for dsh 0.1.5–0.1.7-rc.2. A clean-profile sandbox install registered with the harness. It invokes the shell.

The verdict — Install it, drive day-to-day traffic through keys in the bundled provider registry, and leave the free pool at the tail of a fallback chain.

What it is — Hindsight provides long-term project memory management for coding agents.

Who it is for — Developers using AI coding assistants such as Claude Code for code development should install it. If you use a non-Python language for the agent, you can choose other implementations.

Watch out — The plugin requires an API key or token and will execute shell commands. Sandbox testing has not been performed. No obvious pitfalls found.

The verdict — Without sandbox testing results, I would not install it.

What it is — Connects DeepSeek Harness to an OpenViking server for pre-step recall, profile injection, session capture, viking:// URI guarding, and memory read/write tools.

Who it is for — You keep revisiting the same repo in DeepSeek Harness and lose conventions across sessions, with OpenViking as the place those should live. If in-repo docs and rule files already are your context, or you only open throwaway chats, skip it.

Watch out — It installed on a fresh profile and the harness registered it. A reachable OpenViking server is required, and it executes shell commands.

The verdict — I'll turn it on: the product for me is recall happening before the step, not two more tools the agent might ignore.

What it is — dsh-weknora provides four read-only tools to operate WeKnora knowledge base for DeepSeek Harness.

Who it is for — When using ReAct-agent in DeepSeek Harness to process WeKnora knowledge base, these tools can provide corresponding capabilities. If you do not use DeepSeek Harness for agent tool calls but rely on other integration methods, you do not need this plugin.

Watch out — Needs to provide API key or token. Will execute shell commands. No obvious pitfalls found.

The verdict — I will install it because it provides WeKnora knowledge base's RAG or ReAct-agent answer function.

What it is — Mounts upstream-refreshed model lanes into DeepSeek Harness and exposes a local OpenAI- and Anthropic-compatible proxy.

Who it is for — You are running agent work inside DeepSeek Harness, want DeepSeek V4.1 Flash or MiMo V2.6 in the current session picker, and have no provider key. If the host already talks to a company gateway through one Base URL, a second local proxy is a duplicate hop.

Watch out — In a clean profile it installed and the harness registered it. What you can call depends on this machine's egress; region-blocked models go into a limited group, and the Kilo pool says prompts may be logged. It executes shell commands; the desktop EAC lane also needs GitHub authorization. Docs list dsh 0.1.5 through 0.1.7-rc.2, status beta.

The verdict — I would keep it as a scratch lane, not the production default — the free quota sits upstream, and this plugin cannot promise it will still be there tomorrow.

What it is — A topic-grouped inventory of community plugins for DeepSeek Harness; the repo does not itself extend the agent.

Who it is for — You are running a coding agent in DeepSeek Harness and need tools, a theme, another provider, or a workflow, without a map of what the community already ships. Anyone whose desktop client already embeds dsh-market and can handle those same entries in its UI can ignore this repo.

Watch out — npm install succeeded in our run, but DeepSeek Harness took it as a normal dependency and did not add a profile layer. It can run shell commands, and you may be asked for an API key or token.

The verdict — I would not add the package as a plugin; on 0.2.1+ I would register the index in Discover, and below that I would just read the repo.

What it is — dsh-purge is a DeepSeek Harness plugin that separates prompt rewriting from sandbox policies and allows swapping prompts per model.

Who it is for — In local lab security evaluations using DeepSeek Harness, users needing to separate prompt rewriting from sandbox policies are suitable for installing it. Users not performing local configuration modifications do not need to install it.

Watch out — Installation requires providing an API key or token and will execute shell commands. Sandbox testing passed in a fresh profile with no obvious issues found.

The verdict — If conducting local lab red-team assessments on Harness security configs, I would install it because it separates prompt and sandbox layers for controlled testing.

What it is — A native window around DeepSeek Harness that boots the runtime, writes editable PPTX, and hands a session to a phone.

Who it is for — You run local agents on DeepSeek or a third-party provider on macOS or Windows, and you want the OS folder picker plus profile, sessions, and model settings stored outside the app directory. If your DeepSeek Harness CLI path is already stable and you only need extra skills on the current profile, this listing is the wrong object.

Watch out — A source install never landed in the profile, so Harness does not pick it up as a plugin. The install runs scripts and expects an API key or token. It is an early preview on @deepseek-ai/dsh@0.2.1-rc.2.

The verdict — Until registration lands, this catalog row is a dead plugin install; I would not spend a source build on it.