All plugin categories
DSH Plugin Category

DeepSeek Harness Security & Policy Plugins

Discover DSH plugins for permission controls, security auditing, policy enforcement, plugin vetting, credentials, recovery, and safer agent operation.

1070 indexed pluginsSorted by popularityPage 13 of 30View newestRecently updated
View plugin dsh-browser-fs

dsh-browser-fs

whitefirer/dsh-browser-fs

3GitHub stars
Manifest Valid

A DSH web plugin that lets agents list, read, and write files in a browser-authorized local directory through the File System Access API and a WebSocket relay.

DSH Profile: webv0.2.0MIT
View plugin
View plugin dsh-teacher

dsh-teacher

Yihong89/dsh-teacher

3GitHub stars
Manifest Valid

A DeepSeek Harness Socratic tutoring plugin that turns Markdown question sets into guided practice, quizzes, gap tracking, and spaced retests.

DSH Profile: webv0.3.0MIT
View plugin
View plugin dsh-plugin-directory

dsh-plugin-directory

dingzhenyao/dsh-plugin-directory

2GitHub stars
Manifest Valid

DSH Web GUI plugin: a browsable, searchable, stats-driven directory of GitHub DeepSeek Harness plugins (dsh-plugin topic), with CDN hot update, README-gated install, and live search.

DSH Profile: <profile-name>v0.1.0-rc.1
View plugin
View plugin dsh-custom-mode

dsh-custom-mode

BOWLUNA/dsh-custom-mode

2GitHub stars
Manifest Valid

Custom modes and custom prompts for DeepSeek Harness (dsh): edit a mode's system prompt in the settings page, pick its base mode, switch plugin rows one by one, and keep several assistants side by side — coding, chat or roleplay (RP) personas (multi-mode / multi-agent).

DSH Profile: webv1.9.9MIT
View plugin

About DeepSeek Harness Security & Policy Plugins

Security and policy plugins inspect, restrict, audit, or recover parts of a DeepSeek Harness environment. This category covers permission rules, plugin vetting, configuration audits, credential controls, access gates, rollback and recovery mechanisms, policy enforcement, and security-focused diagnostics. Protection and enforcement levels differ by implementation, so the Registry keeps source and verification evidence visible instead of reducing plugins to a generic safe label.

When evaluating a security plugin, first determine whether it reports findings or actively blocks and modifies behavior. Review its enforcement point, required privileges, documented fail-open or fail-closed behavior, files and credentials it accesses, dependencies, lifecycle scripts, repository activity, and compatibility evidence. A Security Signal describes observable evidence; it is not itself a security certification.