anysearch-dsh

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 — Lets an agent find external endpoints by the job to be done, read params and per-call price, then invoke them with credentials injected server-side.

Who it is for — You are in DeepSeek Harness pulling backlinks, SERP, social, or company enrichment without Semrush-class seats. Skip it if secrets must stay on the caller host, or the environment cannot send traffic to an outside proxy.

Watch out — A clean-profile install completed and the harness registered the plugin. MCP stays disabled until TREG_TOKEN is set, and setup or runtime will run shell. Catalog usage is billed per call; newly verified accounts get a one-time $1.00.

The verdict — Skill is enough to shop the catalog. MCP stays off on my machine until the team is actually routing its own CLIs and skills through the same proxy.

What it is — An ops layer for DSH: extra bash, PowerShell 7, and Rust-backed tools, optional stock-Shell hiding, and on-demand loading so tool traffic stays small.

Who it is for — You are in Native or PTC on DeepSeek Harness, grinding bulk file edits or pdf and word reads, and oversized dumps plus error loops are chewing rounds. If the bill is almost all long reasoning with barely any tool calls, swapping this surface will not move cost.

Watch out — DeepSeek Harness 0.2.2-rc.1 rejects the newest release before install because the declared dsh range omits that version; 0.4.1 installed on the same host. The docs name 0.2.0-rc.2 and 0.2.1-rc.2 as supported hosts. It executes shell commands as part of the job.

The verdict — I would add it pinned to 0.4.1, or let dshmarketplace-cli choose—not latest.

What it is — Hooks a DSH agent into a live local Blender session over TCP, exposing 15 tools plus a 228-op planning layer.

Who it is for — You already run a DSH agent on a machine with Blender 4.x or 5.x—lofting, measuring a reference image, or auditing an assembly—and it still cannot grab a viewport frame or execute Python in that session. If your 3D path never attaches to a local Blender process, there is no session to drive.

Watch out — The sandbox got the package in, then pnpm blocked the build script and Harness never finished registration until that build was allowed by hand. The bundled Blender addon must be enabled first, with Node.js 20+ and Blender 4.x or 5.x. It executes shell commands.

The verdict — Worth it only on a box that already has Blender to connect; I would allow the blocked build first rather than chase a registration that never ran.

What it is — Brings anime torrents from 動漫花園, 蜜柑计划, 萌番组, and ANi into DSH, searchable in chat or a sidebar, plus a season calendar and a floating player.

Who it is for — You are inside a DeepSeek Harness agent picking this season’s release and still leave the session to filter by fansub and type. If MCP or the HTTP API already feeds that index in another toolchain, skip this plugin.

Watch out — This listing has no one-line install; the plugin lives in a repo subdirectory and has to be wired in by hand. It runs shell commands. No sandbox run is on record, so there are no measured pitfalls.

The verdict — I’d add it only if torrent hunting already happens inside DSH most weeks.

What it is — A DeepSeek Harness plugin that drives Tencent CloudBase from the thread: scaffold and deploy full-stack apps, present query results as table cards with paging, sorting and CSV export, preview a release on its domain, and call CloudBase MCP tools after device-code login.

Who it is for — You are shipping a full-stack app from DeepSeek Harness onto Tencent CloudBase and still lack an in-thread MCP bridge plus a DB / Storage / Auth panel. If CloudBase is not the runtime, this is the wrong door; if the Toolkit already lives in another AI IDE and DeepSeek Harness is only a second editor, the gap is not this plugin.

Watch out — On a fresh profile the sandbox install completed and DeepSeek Harness registered it. You still bring the CloudBase environment; login is device-code; shell commands run at runtime. Sensitive actions the agent proposes still need a human yes—the Toolkit does not supply judgment.

The verdict — A clean install is not a reason to add it; I would keep it only when query and release are actually supposed to happen in the DSH thread.