ouli-1242/dsh-plugin-tool-management
C3一个设置面板,统一管理 MCP、技能、记忆、子智能体、提示词和归档会话;可自定义搭配场景,一个场景即可切换整个环境;Agent也能帮你操作这个插件。 | One settings panel managing MCP, skills, memory, subagents, prompts and sessions; customize scene combos to switch the whol
★ 50+ · ouli-1242/dsh-plugin-tool-management source on GitHub · this plugin in the registry
ouli-1242/dsh-plugin-tool-management is a DeepSeek Harness plugin rated C3 — powerful capability combined with sensitive behavior. It patches the dsh runtime, executes system commands, decodes base64 payloads, reads credential-class env vars.
Installable plugin — declares a dsh.bundle manifest
What it can do
| Capability | Flag | Evidence |
|---|---|---|
| patches the dsh runtime | runtime_patch | ./cordis.patch.yml |
| executes system commands | exec | ×8 in authored code, e.g. src/index.ts:164, src/index.ts:3052 |
| decodes base64 payloads | base64_decode | ×2 in authored code, e.g. src/imports/upload.ts:47, src/skills/upload-pipeline.ts:414 |
| reads credential-class env vars | token_env | DSH_PLUGIN_TOOL_MANAGEMENT_TOKEN |
Tool registrations
2 confirmed registration point(s); analysis is incomplete.
src/index.ts:5060tool factorysrc/index.ts:5098tools.registersrc/client/00-prelude.js:56Cannot parse source: Unexpected token (56:5)src/client/40-apply-head.js:492Cannot parse source: Unexpected token (492:54)src/client/90-apply-tail.js:35Cannot parse source: Unexpected token (35:6)
Services it injects
locale sessions timer
Hooks it attaches
agent/pre-step domain/changed
Outbound domains
registry.npmmirror.com your-server.com
Environment variables it reads
USERPROFILE APPDATA DSH_HOME LOCALAPPDATA DSH_PLUGIN_TOOL_MANAGEMENT_TOKEN npm_config_prefix NPM_CONFIG_PREFIX npm_config_cache XDG_CONFIG_HOME DSH_AGENTS_HOME
How to read this
Levels measure capability surface and transparency, not maliciousness. A C3 plugin can be entirely legitimate — a desktop shell genuinely needs subprocesses. The point is that you can see this before installing. See the levels explained and how dsh plugins work.
Findings come from static analysis of shipped code; nothing is executed. Think a flag is wrong? Open an issue — every flag cites the file and line it came from.