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.

1065 indexed pluginsSorted by popularityPage 9 of 30View newestRecently updated
View plugin deepseek-harness-background

deepseek-harness-background

HaoyueQin/deepseek-harness-background

5GitHub stars
Manifest Valid

为 DeepSeek Harness Web GUI 添加自定义背景图片:上传本地图片或粘贴图片链接,可调不透明度、遮罩、面板透明与毛玻璃模糊,带实时预览,5% 阻尼滑块松手即存,遮罩自动适配明暗主题。

DSH Profile: webv0.5.5MIT
View plugin
View plugin agent-guard

agent-guard

mokuyoaxis/agent-guard

5GitHub stars
Manifest Valid

Make destructive AI-agent actions reversible by default — quarantine + audit + human escalation for rm/git destructive operations. Reliability infrastructure, not a sandbox.

DSH Profile: <p>v0.1.1MIT
View plugin
View plugin hermes-dsh-collab

hermes-dsh-collab

Cavan-Ou/hermes-dsh-collab

5GitHub stars
Manifest Valid

Battle-tested multi-agent collaboration playbook for DeepSeek Harness: model-tier routing, spec discipline, git single-writer rule — as an installable skill. 多 agent 管线里运行 DSH 的实战协作规范

DSH Profile: headlessv0.3.1MIT
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.