ModLens
liustack/modlens
2.2kGitHub starsA DeepSeek Harness vision plugin that turns pasted images into structured OCR, layout, and semantic evidence for supported text-only models.
Find and compare community plugins for DeepSeek Harness with source-backed capabilities, install paths, security signals, compatibility evidence, and repository facts.
Browse popular DSH Plugin Registry entries with source-backed install information, repository signals, capabilities, and verification status.
liustack/modlens
2.2kGitHub starsA DeepSeek Harness vision plugin that turns pasted images into structured OCR, layout, and semantic evidence for supported text-only models.
zhu1090093659/dsh-web-ui
2.8kGitHub starsAn installable DSH Web profile bundle adding UI extensions, tools, remote access features, and skins to dsh web.
dsh plugin --profile web add @linxin666/dsh-web-ui-allomdsh-dev/DSH-better-sidebar
1.5kGitHub starsA DSH web plugin that adds a VSCode-like, session-isolated sidebar and bottom workspace.
npx -y --package @deepseek-ai/dsh dsh plugin --profile web add dsh-better-sidebarccch1mneyyy/dsh-TUI
1.4kGitHub starsClaude Code-style full-screen terminal UI plugin for DeepSeek Harness agents.
GanyuanRan/Aegis
1kGitHub starsA multi-host method pack for architecture-aware, evidence-driven AI coding workflows, including DeepSeek Harness.
sandbaseai/sandbase-harness
598GitHub starsA self-hosted AI-agent runtime with a native DeepSeek Harness MCP bundle for managing agents and sessions.
dsh plugin --profile web add managed-agentsAnionex/dsh-vision-toolkit
485GitHub starsA DeepSeek Harness native Profile Bundle that adds agent-scoped image analysis, OCR, image grounding, UI restoration, pixel comparison, artifacts, and Web settings.
**Install:** dsh plugin --profile web add @anionex/dsh-vision-toolkitmnemon-dev/mnemon
457GitHub starsA standalone, local persistent-memory system for AI agents, with DeepSeek Harness support provided through the separate dsh-mnemon plugin.
dsh plugin --profile web add dsh-mnemonccch1mneyyy/working-activity
644GitHub starsA DeepSeek Harness activity-status plugin that shows live agent work in supported terminal and Web UI consumers.
| DeepSeek Harness | dsh-working-activity | [packages/activity/working-activity/](packages/activity/working-activity/) | dsh plugin --profile <profile> add dsh-working-activity |dsh-market/dsh-market
453GitHub starsAn in-DeepSeek Harness visual plugin marketplace for browsing, searching, installing, updating, and removing community plugins.
dsh plugin --profile web add dshmarketNagi-ovo/dsh-ads
445GitHub starsA DeepSeek Harness web UI plugin that adds intentionally fictional, early-2000s-style parody ads and reward-gate interactions.
dsh plugin --profile web add github:Nagi-ovo/dsh-adsNanmiCoder/dsh-agent-teams
344GitHub starsA DeepSeek Harness plugin that coordinates captain-led multi-agent teams with dependency-aware tasks, durable messaging, and a live web activity panel.
dsh plugin --profile web add @nanmicoder/dsh-agent-teamsBrowse DeepSeek Harness plugins by capability, from vision and Web UI to terminal workflows, security, skills, and remote execution.
Understand plugins before you install
Public repository evidence is analyzed to explain what a plugin does, which capabilities it adds, useful scenarios, who it fits, and documented limitations.
Dependencies, lifecycle scripts, licenses, package manifests, DSH bundle declarations, and public source availability are surfaced as objective security signals.
Version-specific runtime results connect DeepSeek Harness releases with the plugin builds tested against them, while untested combinations are shown clearly.
Installable plugins and plugin bundles are separated from directories, SDKs, scaffolds, desktop wrappers, tutorials, and other resources through rules, AI analysis, and review.
Each repository moves through a structured registry pipeline that combines public source facts, AI-assisted analysis, deterministic rules, and conservative publication policy.
Find DeepSeek Harness plugin repositories from the public dsh-plugin ecosystem and community submissions.
Read README content, package metadata, DSH bundle declarations, manifests, releases, repository activity, and install information.
Build source-grounded intelligence for capabilities, use cases, target users, documented limitations, install paths, and security signals.
Classify the artifact and plugin type, then combine deterministic evidence, AI analysis, and registry policy to approve, reject, or hold it for review.
Publish index-ready plugin pages with install commands, repository facts, security signals, related plugins, and version-specific compatibility evidence.
DeepSeek Harness is built around a plugin-first architecture, so capabilities can be added or replaced without turning every feature into a core change. A DeepSeek Harness plugin can provide model tools, reusable skills, Web UI components, terminal experiences, runtime services, storage, sandboxes, model integrations, workflow logic, or other agent capabilities.
Plugins are usually installed into a DSH profile, which means the same Harness installation can run different combinations of extensions for Web, terminal, headless, or specialized workflows. That flexibility makes plugin discovery, source quality, security signals, and version compatibility increasingly important as the DSH ecosystem grows.
Developers publish community plugins through public GitHub repositories and the dsh-plugin ecosystem. DSH Plugin is an independent DeepSeek Harness plugin directory and registry that organizes those projects by capability, derives install paths from public source evidence, analyzes repository and package metadata, and publishes structured intelligence, security signals, and compatibility evidence so users can compare DSH extensions before installing them.
$ dsh plugin --profile web add <package-or-git-spec>Install DSH plugins
Most DeepSeek Harness plugins are installed into a specific DSH profile with the dsh plugin command. The install target can be an npm package, a Git repository spec, or another source supported by the plugin author. DSH Plugin keeps the install path tied to public repository and package evidence so you can verify the target before running it.
$ dsh plugin --profile web add <package-or-git-spec>Check whether the extension targets the web, terminal, headless, or another profile. Installing a plugin into the wrong profile may leave its UI or runtime capabilities unavailable.
Copy the install command associated with the plugin repository. Some projects publish to npm, while others are installed directly from GitHub or a local checkout.
Long-running DSH profiles may need a restart after installation. When the author provides a dump-config, health-check, or verification command, run it before relying on the extension.
Before installing any third-party DSH plugin, review its repository, recent activity, license, package metadata, install scripts, requested capabilities, security signals, and compatibility evidence. These signals make the review clearer, but they do not replace your own trust decision for code that will run on your machine.
Understand DSH profiles, package specs, Git sources, and the dsh plugin install command.
Read guideA practical path from DSH bundle metadata and package structure to a shareable plugin.
Read guideLearn the concepts behind how DeepSeek Harness plugins and plugin bundles are composed.
Read guideA DSH plugin is an extension that adds or changes capabilities in DeepSeek Harness, such as tools, skills, UI, model integrations, runtime services, storage, security controls, or workflow features.
Most plugins are installed into a DSH profile with a command such as dsh plugin --profile web add <package-or-git-spec>. The exact profile and package or Git spec depend on the plugin, so use the project’s documented target and restart the profile when required.
DSH Plugin indexes public community repositories from the dsh-plugin ecosystem and structured submissions from plugin authors and users. Repositories then pass through source inspection, classification, AI-assisted analysis, and registry policy before publication.
No. Indexed means the repository has been accepted into the public DSH Plugin Registry. Runtime Verified is reserved for plugin and DeepSeek Harness version combinations backed by published runtime compatibility evidence.
Third-party plugins execute code and should be reviewed before installation. DSH Plugin surfaces objective security signals such as dependency counts, lifecycle scripts, licenses, package manifests, DSH bundle declarations, and source availability, but no signal is an absolute safety guarantee.
Use Submit Plugin and provide the public GitHub repository URL. The submission enters the same discovery, inspection, analysis, classification, review, and publication pipeline used by the registry.
Submit the public GitHub repository so DSH Plugin can analyze it, classify it, and make the plugin discoverable in the registry.