All plugin categories
DSH Plugin Category

DeepSeek Harness Developer Tools & Plugins

Discover DSH plugins for coding, Git, repository navigation, file operations, debugging, reviews, development workflows, and engineering productivity.

2374 indexed pluginsSorted by popularityPage 8 of 66View newestRecently updated
View plugin reef

reef

huey1in/reef

20GitHub stars
Manifest Valid

A DeepSeek Harness bundle combining browser automation, MCP serving, GitHub/GitLab workflows, and a native in-app panel.

DSH Profile: webv1.5.2MIT
View plugin
View plugin dsh-plugin-product-subagents

dsh-plugin-product-subagents

shaokeyibb/dsh-plugin-product-subagents

19GitHub stars
Manifest Valid

Role-based Codex / Claude Code / ACP subagent providers for the DeepSeek Harness — continuable children, durable session recovery, per-role product permissions, and delegation with a permission ceiling.

DSH Profile: webv0.4.0MIT
View plugin
View plugin dsh-read-url

dsh-read-url

2672243194/dsh-read-url

18GitHub stars
Manifest Valid

DeepSeek Harness URL reader: fetch any page and return clean main-content text/Markdown. Auto charset (GBK/GB2312/UTF-8/Big5), token-efficient (6000-char cap, cache, offset), zero deps, no API key. 网页一键读全文 → 干净正文 / 结构化 Markdown

v1.9.0MIT
View plugin

About DeepSeek Harness Developer Tools

Developer-tool plugins extend DeepSeek Harness around the day-to-day mechanics of software work. This category covers Git and repository views, file navigation, change review, code references, debugging helpers, development metrics, workspace tooling, build or runtime controls, and automation around common engineering tasks. These plugins are grouped here to make developer-facing capabilities easier to compare without mixing them with unrelated UI or general-purpose extensions.

Developer-tool plugins often operate close to repositories, files, shells, Git operations, and development environments. Before installing one, review its requested capabilities, lifecycle scripts, dependencies, write access, shell behavior, source activity, license, and compatibility evidence. A useful developer plugin should improve the workflow without obscuring what code or system access it requires.