KardDev/dsh-plugins

A small, young plugin collection for people already using DeepSeek Harness (DSH): one plugin adds an English motion/UI workspace, the other tracks what each session costs. Its value is directly tied to whether DSH is part of your workflow.

The problem

Working inside a coding agent, you often want two things the base harness does not surface: a way to draft and preview animated interfaces while you talk through changes, and a running account of how much each session is spending across providers and models. Without them, motion work means leaving the agent for a separate animation tool, and cost awareness means checking provider dashboards after the fact. These plugins move both into the DSH session itself, so the output is an editable motion canvas or MP4 locally, and a per-session cost breakdown rather than end-of-month guesswork.

What's different

The motion plugin is an English-localized derivative of an existing dsh-motion-ui project, with HTML/SVG canvases, editable motion and local MP4 production described in its plugin directory. The cost plugin covers per-session API spend, breaks it down by provider and model, and can optionally discover pricing automatically, per its plugin page. That split is the practical benefit: one plugin handles creative output, the other handles observability, and each is versioned independently so you can adopt just one.

The main trade-off is scope. This is not a general animation suite or a general cost dashboard; both plugins are built for the DSH host and are useful only inside it. The motion plugin being a derivative also means its lineage matters if you are comparing it to the upstream project. Cost figures depend on pricing data, and the README only describes auto-discovery as optional, so the accuracy question is one to check in the plugin's own documentation rather than assume.

Who should try it

Good fit: a DSH user who regularly produces motion or UI mockups in conversation and wants local MP4 output without switching tools, or a team lead who needs session-level spend visibility across models. Installing only the cost plugin into a named profile is a documented path for the second case. Poor fit: anyone not running DSH, since neither plugin has a standalone mode, and anyone wanting a broad animation editor or a cross-tool billing platform.

Requirements and limitations

You need DSH itself and a checkout-based install: the README instructs cloning the repository, installing with pnpm, and adding each plugin by local path because package managers resolve Git dependencies at the repository root. The short npm-style form only works once a plugin is published there. The workspace uses hoisted dependencies, and the README notes this matters on Windows because the plugin build runs esbuild through Node's child_process and symlinked per-package node_modules does not resolve reliably there.

Upkeep is per plugin: each keeps its own README, tests, license and third-party notices, so licensing and obligations differ between the two. The repository declares no top-level license, so check the plugin directory before redistributing. After installing, the host must be restarted and the page reloaded.

HotRepo's take

HotRepo first recorded this repository at 5 days old, with 287 total stars and #25 on the NEW-REPOSITORY board for JavaScript on 2026-10-26 — a snapshot, not a daily growth figure. With only one recorded date and no comparable daily-board history, persistence cannot yet be judged. Before investing, verify the motion plugin's current divergence from its upstream in the plugin README, since that determines whether fixes there reach this fork.