Search an independent catalog of DeepSeek Harness plugins by capability. Compare bundle verification, repository activity, compatibility notes, and install commands before adding code to a DSH profile.
OpenViking memory and context bundle for DeepSeek Harness: pre-step auto-recall and profile injection, session capture, `viking://` URI guarding, and recall/write memory tools backed by an OpenViking server.
dsh plugin --profile default add github:volcengine/OpenViking#path:/examples/dsh-memory-plugin
Hindsight, agent memory that learns: long-term project memory with auto recall and retain, knowledge pages, deep reflection, and per-repo memory banks.
dsh plugin --profile default add github:vectorize-io/hindsight#path:/hindsight-integrations/coding-agents
Generate validated, self-contained interactive architecture, workflow, sequence, data-flow, and lifecycle diagrams from repositories or system descriptions.
dsh plugin --profile default add github:tt-a1i/archify#path:/integrations/deepseek-harness
Config-only bundle that mounts Ouroboros through the DSH MCP client, exposing 36 interview, Seed, execution, evaluation, and evolution workflow tools in DSH.
dsh plugin --profile default add github:Q00/ouroboros#path:/integrations/dsh-plugin
Plugin and skin collection for the DSH Web UI: task board, Git graph, right-side panel, remote mobile UI, pet, live token stats, and a skin center.
dsh plugin --profile default add github:zhu1090093659/dsh-web-ui#path:/packages/dsh-web-ui-all
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.
dsh plugin --profile default add github:strukto-ai/mirage#path:/typescript/packages/dsh
Free vision for text-only agents: built-in keyless vision chain plus pixel tools (Q&A, grounding, crop, pixel diff, colors, OCR, SVG trace, cutout, screenshots); paste an image to use it.
dsh plugin --profile default add github:ysr666/dsh-vision-router
Claude Code-style full-screen terminal UI: pixel-whale header, live status line, and streaming thought expansion.
dsh plugin --profile default add github:ccch1mneyyy/dsh-TUI
Four GitHub workflow skills for PR triage, review feedback, GitHub Actions diagnosis, and safe draft-PR publishing, reusing existing DSH capabilities with gh/git fallbacks.
dsh plugin --profile default add github:Starfie1d1272/dsh-github-skills
Vision bridge for text-only models: paste an image, get structured JSON evidence (OCR, layout, semantics).
dsh plugin --profile default add github:liustack/modlens
Plugin manager with a rescue center: grouped enable/disable by necessity, multi update sources (npm / dshfind market / GitHub), browser-first downloads with an auto-install folder, P2P fallback, pre-boot self-check and broken-bundle quarantine.
dsh plugin --profile default add github:nonentity303/dsh-plugin-manager
DeepSeek Harness plugins are installable Cordis bundles that add or replace parts of the agent runtime. A plugin can provide models, tools, skills, sessions, storage, sandboxes, scheduling, or a different interface. Read the official Harness overview.
This directory indexes public repositories and explains what each bundle does, where it comes from, and how its install target is declared. DSH Plugins is independent from DeepSeek and does not run third-party code for you. Inspect the official source repository.
DSH plugins can work at several layers of the harness. Match the layer to the capability you need, then review the access that layer requires.
| Plugin layer | What it can add | Check before installation |
|---|---|---|
| Models and tools | Connect a model provider or add browser, vision, search, command, and MCP capabilities. | Confirm the required API keys, network access, and external services. |
| Memory and sessions | Persist preferences, search prior sessions, import chats, or replace session storage. | Review what data leaves the machine and where the plugin stores it. |
| Interfaces and workflows | Replace the Web UI, add a terminal interface, or package repeatable agent workflows. | Match the plugin to the profile and DSH version it supports. |
| Runtime components | Change sandboxes, scheduling, storage, subagents, or the agent loop itself. | Treat shell access and build scripts as privileged code. |
Start with the part of your current workflow that is missing or repetitive. The plugin name matters less than the access it needs and the work it removes.
Describe the capability you need, browse a category, or search a package name from one catalog.
See whether the source declares a DSH bundle and whether the directory can produce an install command.
Use repository activity, license, compatibility notes, and editorial context before choosing a plugin.
A valid bundle manifest proves structure, not security. Review the repository before running any dsh plugin command.
Prefer the maintainer's repository or published package. Make sure the command names the expected owner, package, branch, and subdirectory.
Check package.json and the dsh.bundle patch. Git and package installs can execute project code during installation.
A plugin may receive shell, filesystem, network, or provider credentials through its profile. Limit access to what the capability needs.
Read the supported DSH version, recent releases, open issues, and latest repository activity before adopting it.
Use a published version, tag, or commit when available. Record the profile and install source so you can update or remove the plugin later.
See how this directory assigns quality tiers and verification labels .
Describe the capability you need, search a known name, or open a plugin category.
Read each summary and compare bundle status, activity, license, and supported workflow.
Check the repository, install target, build scripts, required credentials, and DSH profile.
Copy the listed command, run it for the intended profile, and confirm that DSH loads the bundle.
The dsh plugin command forwards an install source to the selected profile. The source format affects reproducibility, review effort, and how updates are delivered.
Every install command needs an explicit profile. Replace a sample profile only after checking where the plugin expects to run.
A DSH plugin is an installable Cordis bundle that extends DeepSeek Harness with a model provider, tool, memory service, interface, workflow, or runtime component. Its package declares a dsh.bundle patch so the selected profile can mount the plugin without editing the Harness source.
Open a plugin page, review its source and requirements, then copy the listed dsh plugin command. Run it with the profile that should receive the bundle. The source may be a published package, Git repository, subdirectory, or local path, depending on the maintainer's release method.
Bundle Verified means the directory found a DSH bundle declaration and could resolve its declared source or entry point. It checks the shape of an installable bundle. The label does not audit the plugin's code, permissions, network requests, dependencies, or behavior after installation.
Safety depends on the plugin's source, dependencies, scripts, requested access, and maintenance. Read the repository and install command before running it. Pay close attention to shell and filesystem access, provider credentials, network calls, build scripts, and unpinned Git sources. Test unfamiliar plugins in an isolated profile.
Yes. DeepSeek Harness treats models, tools, sessions, storage, sandboxes, interfaces, scheduling, and parts of the agent loop as composable plugins. That flexibility lets developers replace runtime behavior, which also means a plugin can have broader access and impact than a prompt-only skill or standalone MCP server.
DSH Plugins is an independent community directory and is not affiliated with DeepSeek. It indexes public repositories, checks bundle structure, records repository signals, and publishes editorial summaries. Treat those labels as research aids. Review the original source and current documentation before installing any third-party code.
Open Submit Plugin and provide the public GitHub repository URL plus a contact email. The review process fetches repository metadata, looks for a DSH bundle declaration, and checks whether the source supports a usable install command. Accepted listings receive a public page and remain linked to their original repository.
Give your plugin a dedicated page, editorial review, and searchable exposure to DSH developers.