DSH Marketplace
中文

plugin-registry

vlln/plugin-registry

Ecosystem infrastructure: a thin browser console for managing official repository plugins (zero patches) plus a make-dsh-plugin skill for guided plugin development.

546TypeScriptMITSource

Install

Add plugin-registry to DeepSeek Harness

via GitHub · GitHub source

Installing from GitHub runs the project's build script, which pnpm blocks until you allowlist it — run the command once and pnpm prints the exact key to add under `allowBuilds` in ~/.dsh/profiles/web/pnpm-workspace.yaml.

What happened when we ran it

Installed cleanly when we ran it

Every command here is run in a throwaway container against a clean profile, and the result is whatever the harness recorded — not a guess from the source. Last run 2d ago.

Due diligence

Before you install plugin-registry

  • Source of record: vlln/plugin-registry — present in the community registry that DSH's own plugin market installs from.
  • Licensed under MIT.
  • A listing here is not a security review. Plugins run with your agent's permissions.

The AI take

What it is — A thin browser console for managing DeepSeek Harness profile plugin installation states, plus a make-dsh-plugin skill for guided official plugin development.

Who it is for — When developing third-party DeepSeek Harness plugins or maintaining plugin lists inside profiles, this console displays installation states and supplies development guidelines. If you only run pre-built official plugins and never create new ones, you do not need to install it.

Watch out — It was successfully installed in a fresh profile and registered by Harness. No obvious issues were found, though the plugin-type comparison and gotchas section in the skill references should be reviewed before any development.

The verdict — I would install it for the development standards it supplies, but it is not essential if the only task is to run existing official plugins.

Generated by grok-4.6, and a starting point rather than a verdict. Where it says a plugin installs or does not, that is from a real run in a clean profile — everything else is read off the repository. Trust the source over this.

What plugin-registry does

Abstract diagram of packages splitting into bundle and configuration paths before converging into one layered structure.

plugin-registry is a DeepSeek Harness plugin that adds a thin browser console for managing plugins in a profile and provides the make-dsh-plugin skill for plugin development.

The console works with the web profile’s existing installation mechanism rather than applying patches. Its install area accepts an npm package name or a GitHub repository reference, normalises the reference, and runs the profile installation flow. Bundle packages are added to the dsh.profile.bundles layer stack; non-bundle Cordis packages are mounted through an insert entry in cordis.patch.yml, where configuration hot reload applies changes. The loaded-plugin area supports version checks, updates, persistent disabled state, and bundle removal. The console also exposes four agent tools for managing this state.

DeepSeek Harness already supplies the plugin runtime and profile bundle mechanism, so plugin-registry is not a replacement runtime or a return of the removed repository-plugins mechanism. It is aimed at developers who want browser-based profile management or guided creation of official-format bundle and Cordis plugins. It is the wrong choice when the built-in profile installation flow is sufficient, or when a project needs the former repository-plugin system rather than the current web-profile path.

plugin-registry documentation

How plugin-registry behaves

DeepSeek Harness loads the console into the web profile. After the plugin is mounted and the Web page is refreshed, a 插件管理 panel appears in the settings page. The panel has two areas:

  • The install area accepts an npm package name or https://github.com/o/r, github.com/o/r, or github:o/r repository reference. GitHub references are normalised before the profile installation flow runs.
  • The loaded-plugin area checks versions, performs updates, persists disabled state, and uninstalls bundle plugins.

The console also provides four agent tools for managing the profile’s plugin installation state.

Configuring plugin-registry

The console writes to the profile structures used by DeepSeek Harness:

  • Bundle plugins enter the dsh.profile.bundles layer stack.
  • Non-bundle, pure Cordis plugins are mounted through an insert entry in cordis.patch.yml.

Changes to the insert configuration take effect through configuration HMR. The README does not specify additional configuration keys or defaults for plugin-registry.

Commands and development guidance

The profile-scoped add operation is the installation entry point used by DeepSeek Harness. The console accepts npm and GitHub sources through that flow; it does not describe a separate package registry or historical repository-plugin command.

The make-dsh-plugin skill documents how to create either an official bundle or a pure Cordis plugin. Its guidance covers choosing a plugin shape, declaring dsh.bundle or a pure apply, and verifying installation. Supporting detail is kept under skills/make-dsh-plugin/references/, including gotchas.md; the console itself is the repository’s reference implementation.

Known limits

The current design depends on DeepSeek Harness profile installation, specifically the web profile for the documented console setup. The former repository-plugins mechanism was removed upstream; plugin-registry does not restore it and instead uses bundle layers or cordis.patch.yml insert entries.

Written from the project's own documentation and kept in sync with it. Where the two disagree, the source is authoritative — read the README on GitHub

Same category

Alternatives to plugin-registry

mirage

strukto-ai

3.5k

Swaps the filesystem and bash providers for a mirage virtual workspace: file tools and shell commands run over mounted resources (RAM, S3, Redis, Slack, Gmail, Notion, Postgres) instead of the host disk, with per-mount read/write/exec modes, per-command sandbox routing (monty, pyodide, quickjs in process; docker, e2b, daytona remote), and installed CLIs (git, gh, slack, linear, ntn, gws, or one you register) as head words in the virtual terminal.

No one-line install — this plugin lives inside a larger repository and publishes no npm package.

GitHub sourceTypeScript2d ago

AI review

mirage

What it is — mirage provides a unified virtual filesystem for AI agents, allowing bash tools to operate across mounted resources.

Who it is for — It is suitable for AI agents that use bash tools and need to access multiple backends such as S3 and Slack at the same time. It is not suitable for agents that only run on local filesystems without remote mounted services.

Watch out — No obvious issues found. There is a static check prompt indicating it will execute shell commands. Sandbox testing was not performed.

The verdict — I would not install it because sandbox testing was not performed.

Generated by grok-4.6, and a starting point rather than a verdict. Where it says a plugin installs or does not, that is from a real run in a clean profile — everything else is read off the repository. Trust the source over this.Read the source
1Details

oh-dsh

hust-open-atom-club

239

Community distribution: TUI, desktop, and Web UI as one bundle with layered installation.

Installed cleanly when we ran it

GitHub sourceTypeScript2d ago

AI review

oh-dsh

What it is — DeepSeek Harness community distribution bundles TUI, desktop and Web UIs.

Who it is for — Developers needing to use DeepSeek Harness for local AI agent coding with workspace capabilities should install it. Users only relying on cloud model services without local tools can skip this.

Watch out — Source installation requires Node.js and build tools. Sandbox test passed, registered in new profile. No obvious issues found.

The verdict — I would install it because it unifies three interfaces for DeepSeek Harness local development, but the tradeoff is building from source.

Generated by grok-4.6, and a starting point rather than a verdict. Where it says a plugin installs or does not, that is from a real run in a clean profile — everything else is read off the repository. Trust the source over this.Read the source
Details

forkprobe

Jayden-X-L

67

Compare multiple skills on the same task and pick the winner.

Installed cleanly when we ran it

GitHub sourcePython5d ago

AI review

forkprobe

What it is — forkprobe is an AI skill selection tool. It runs multiple skills in parallel on the same task, generates a local HTML report, and lets you choose the winner.

Who it is for — When you are unsure which skill fits the current task and want to review real outputs before deciding, forkprobe is suitable to install. People who do not need skill comparison for simple deterministic tasks do not need to install it, because the answer or tool path is already clear and direct execution is faster.

Watch out — Installing forkprobe from GitHub source requires manually allowing the build script. Sandbox testing passed: it installs in a fresh profile and registers into the profile via Harness. No obvious issues found.

The verdict — I would install it because it generates continuation handoff after selecting the winner and supports anonymous sharing of the choice.

Generated by grok-4.6, and a starting point rather than a verdict. Where it says a plugin installs or does not, that is from a real run in a clean profile — everything else is read off the repository. Trust the source over this.Read the source
1Details

dsh-multica-runtime

forrestchang

46

Run the dsh runtime on Multica.

Installed cleanly when we ran it

GitHub sourceTypeScript5d ago

AI review

dsh-multica-runtime

What it is — Private runtime bridge between Multica and DeepSeek Harness.

Who it is for — Developers needing DSH runtime integration in the Multica environment. For developers using standard DSH environments, this bridge serves no purpose.

Watch out — Sandbox test passed: installed in a new profile and registered with harness. The plugin executes shell commands.

The verdict — I would install it because it requires no changes to DeepSeek Harness.

Generated by grok-4.6, and a starting point rather than a verdict. Where it says a plugin installs or does not, that is from a real run in a clean profile — everything else is read off the repository. Trust the source over this.Read the source
1Source

dsh-plugin-check

omdsh-dev

24

Plugin health checks: manifest protocol / patch format / build traps, zero-dependency and read-only.

Installed cleanly when we ran it

GitHub sourceTypeScript2d ago

AI review

dsh-plugin-check

What it is — This is a zero-dependency read-only DeepSeek Harness plugin health check tool that scans plugin repositories and outputs compliance reports on manifest protocols, patch formats and build traps.

Who it is for — When you maintain multiple DeepSeek Harness plugin repositories in your organization and need regular checks on manifest protocols, patch formats and build traps, this tool fits your use case. If you only run a single plugin or your repository has already passed manual review, you do not need this tool.

Watch out — Sandbox testing passed: installed in a fresh profile and registered into harness. Static checks may mention executing shell commands but do not execute them. No other obvious issues found.

The verdict — I would install it because it provides automated compliance checks that reduce integration pitfalls in organizational plugin workflows, but only if installed via the profile bundle method.

Generated by grok-4.6, and a starting point rather than a verdict. Where it says a plugin installs or does not, that is from a real run in a clean profile — everything else is read off the repository. Trust the source over this.Read the source
1Source

dsh-user-experience

DietCokewithSugar

19

Finds potential UX issues in your project: automatically reviews React/TypeScript code, pinpoints each problem, and gives concrete suggestions.

Installed cleanly when we ran it

npm packageTypeScript2d ago

AI review

dsh-user-experience

What it is — Scans React, TypeScript, JavaScript, and Vue 3 code to simulate user personas, detect UX issues, and provide concrete suggestions.

Who it is for — When developing a React application with DeepSeek Harness and needing UX simulation capabilities, this plugin is suitable. If your project uses Svelte or Vue 2 frameworks, you do not need to install this plugin, as it does not support analysis for those languages.

Watch out — Sandbox test passed successfully with installation and registration in a fresh profile and no obvious issues found. It can obtain browser evidence when rendered page support is available, but relies only on static evidence without browser environment.

The verdict — I would install it because it automatically runs the walkthrough after file edits and provides locatable UX optimization suggestions.

Generated by grok-4.6, and a starting point rather than a verdict. Where it says a plugin installs or does not, that is from a real run in a clean profile — everything else is read off the repository. Trust the source over this.Read the source
Source