oomol-lab/dsh-oomol
C3OOMOL Connector for DeepSeek Harness—discover connected apps and execute Actions through progressive MCP discovery without exposing provider credentials.
★ 10+ · oomol-lab/dsh-oomol source on GitHub · this plugin in the registry
oomol-lab/dsh-oomol is a DeepSeek Harness plugin rated C3 — powerful capability combined with sensitive behavior. It patches the dsh runtime, executes system commands, reads credential-class env vars.
What it can do
| Capability | Flag | Evidence |
|---|---|---|
| patches the dsh runtime | runtime_patch | ./cordis.patch.yml |
| executes system commands | exec | ×3 src, e.g. scripts/doctor.mjs:1, scripts/doctor.mjs:1 |
| reads credential-class env vars | token_env | OOMOL_CONNECT_RUNTIME_TOKEN, OOMOL_MCP_API_KEY |
Services it injects
connection layout locale settings slots tools
Hooks it attaches
credentials/updated
Outbound domains
console.oomol.com connector.oomol.com oomol.com
Environment variables it reads
OOMOL_MCP_API_KEY OOMOL_CONNECT_RUNTIME_TOKEN
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.