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 8 of 30View newestRecently updated
View plugin dsh-cursor-subscription

dsh-cursor-subscription

orrinzeng/dsh-cursor-subscription

6GitHub stars
Manifest Valid

Log directly into your Cursor account within DeepSeek Harness and use your Cursor subscription — no API Key required, and no dependency on Cursor IDE or Cursor CLI. 在 DeepSeek Harness 中直接登录 Cursor 账户并使用 Cursor 订阅,不需要 API Key, 也不依赖 Cursor IDE 或 Cursor CLI。

DSH Profile: webv0.6.9MIT
View plugin
View plugin dsh-qqbot

dsh-qqbot

gcry13067381632-jpg/dsh-qqbot

6GitHub stars
Manifest Valid

AI 统管 QQ 群组:审核放行、群发文件、沟通其他web会话的ai! 气氛组担当:表情包自动入库,AI 自己决定开口,多预设多人格轮班陪聊! 远程办公:权限审批、提问卡片转发qq

v1.5.5MIT
View plugin
View plugin dsh-skills-anywhere

dsh-skills-anywhere

noteflowai/dsh-skills-anywhere

6GitHub stars
Manifest Valid

Reuse Agent Skills across DeepSeek Harness and MCP. Check local SKILL.md files in the browser or CI, with parser diagnostics, file hashes and clear exit codes. Try the Hugging Face playground.

DSH Profile: webv0.12.1MIT
View plugin
View plugin dsh-smart-restart

dsh-smart-restart

edusrez/dsh-smart-restart

6GitHub stars
Manifest Valid

Wakes the main agent after any DSH restart so interrupted work resumes automatically — adds a restart tool and an optional canary that validates the boot and warns instead of breaking.

DSH Profile: <name>v0.5.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.