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.

596JavaScriptMITSource

Install

Add plugin-registry to DeepSeek Harness

Install into

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 todayon DeepSeek Harness 0.2.2-rc.5.

Show it in your README

install verified — dshmarketplace

For maintainers: the badge serves this listing's latest sandbox verdict, so a re-run updates it on its own — and it links readers to the full result here.

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.

Security

What installing plugin-registry runs

Build scripts

No build script was blocked in our run.

Source: our sandbox install on DeepSeek Harness 0.2.2-rc.5, today.

Install hooks

package.json declares no preinstall, install or postinstall script.

Source: package.json on GitHub, read at our last sync. prepare is not recorded; it runs only on a GitHub install, and shows up under build scripts when pnpm blocks it.

README mentions

Neither shell commands nor credentials.

Source: a keyword match on the README — a hint about what the plugin touches, not an analysis of its code.

Not an audit. These are the record of one install and two text scans; nobody has read this plugin's code on your behalf. Plugins run with your agent's permissions.

The AI take

What it is — It is infrastructure providing a thin browser console and make-dsh-plugin skill for the DeepSeek Harness plugin ecosystem.

Who it is for — If you need to manage plugin installation states in your DeepSeek Harness profile and want the make-dsh-plugin skill for developing official plugins, this fits.

If you only use existing plugins without needing management or development tools, you don't need this because it focuses on ecosystem infrastructure rather than direct runtime features.

Watch out — It was tested to install successfully in a fresh profile and register with harness.

Note the specific #path: format required for git source installation on Windows to prevent command splitting.

No other obvious issues found.

The verdict — I wouldn't install it because it serves as infrastructure rather than a functional plugin; if your use case doesn't involve plugin development or state management, it's not worth it.

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

7.0k

One repository, three parts: a runtime injector for DSH plugin packages (inject, hot-reload, unload, promote a dev staging tool to the front, route self-heal, plus a settings-page plugin manager that lists, unloads and drags folders in to internalize), a task-aware reasoning-mode router agent preset (router-standard / router-spec / router-react), and a graded two-level task protocol whose six tools (commit_star, lock_stage, revise_do, edit_plan, mark_task, redteam_verdict) pin task state to disk. The injector implementation ships in-tree, so the install carries its own behaviour rather than a dependency list.

Installs, but needs a build approved first

GitHub sourceJavaScript2mo ago

AI review

dsh-routing-suite

What it is — A DSH suite that ships a runtime injector, task-aware reasoning-mode presets, and a graded two-level protocol whose six tools pin task state to disk.

Who it is for — You are on DSH 0.1 preview with DeepSeek Pro or Flash, running spec-then-execute work that needs the agent to switch reasoning modes by task and to write stage state to disk. Skip it when your DSH is already outside >=0.1.0-rc.6 <0.2.0; the preview still breaks APIs, so the version window is the constraint, not the job type.

Watch out — In our run the install started, then pnpm blocked the build script and DSH never finished registration. Until that build is allowed by hand, the plugin does not actually land.

The verdict — I'll take it only after unlocking the blocked build: the injector ships in-tree, so that allow step is how you accept this runtime's behaviour rather than a dependency list.

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

mirage

strukto-ai

3.7k

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 sourceTypeScript28d 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-my-agent

first-fluke

1.4k

Runs project OMA checks before and after tool execution and when a turn tries to finish. Installs its OMA CLI dependency and initializes unconfigured projects on first use. Requires Node.js 22+; initial setup needs network access and project write access.

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

GitHub sourceTypeScript28d ago

AI review

oh-my-agent

What it is — oh-my-agent runs project OMA checks before and after tool execution and when a turn tries to finish, installing its OMA CLI dependency and initializing unconfigured projects on first use.

Who it is for — It fits users who need to run project checks before and after tool execution and when a turn tries to finish, as well as project initialization on first use. Users who avoid network access and project write permissions during setup can choose not to install it.

Watch out — Initial setup requires network access and project write access. It executes shell commands. Sandbox testing has not been performed, no obvious pitfalls found.

The verdict — I won't install it because it requires network access and project write access during initial setup and has no sandbox testing.

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
386

Manages local DeepSeek Harness skills in Settings and shows shared Agent skills as read-only.

Installed cleanly when we ran it

npm packageJavaScript23d ago

AI review

dsh-skills-manager

What it is — Manages local DeepSeek Harness skills in Settings and displays shared Agent skills as read-only.

Who it is for — Users who need to manage local and project skills across multiple tools in DeepSeek Harness setups would use this plugin. Users who only rely on shared agent skills without local or project management do not need it.

Watch out — Passed sandbox test: installed in a new profile and registered by Harness. No obvious issues found. Compatible with DeepSeek Harness 0.2.x series.

The verdict — I would install it because it supports incremental updates from public GitHub repositories with backup restoration.

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

oh-dsh

hust-open-atom-club

323

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

GitHub sourceTypeScript2mo ago

pi2dsh

weijiafu14

212

Pi Host ABI compatibility engine: after one install, unmodified Pi extensions from npm mount as native DSH plugins with `dsh plugin add <pi-package>`. Verified end to end on stock DSH with pi-mcp-adapter (full MCP manager: OAuth, resources, prompts, MCP Apps, elicitation, sampling), @tintinweb/pi-subagents, pi-code, pi-hermes-memory and pi-background-tasks; `pi2dsh inspect` reports a package's compatibility before installing.

DeepSeek Harness 0.2.2-rc.5 refuses the latest release

npm packageTypeScript25d ago

AI review

pi2dsh

What it is — pi2dsh is a Pi host ABI compatibility engine that mounts unmodified Pi npm packages as native DSH plugins on DeepSeek Harness.

Who it is for — Pi plugin developers who want to run their npm packages unmodified on DeepSeek Harness should install it. Developers who are not involved in Pi plugin development do not need to install it.

Watch out — It was tested successfully in a new profile and registered into the profile. A restart of DeepSeek Harness is required. Installation may require manually approving build scripts if pnpm blocks them.

The verdict — I would install it if I need Pi ecosystem plugins on DeepSeek Harness because it provides unmodified compatibility.

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