lishize20040802-rgb/dsh-deep-ptc-mode
C2Deep PTC mode for DSH: fixes reporting, asking, reachability, planning and context/token use; plugin-first with official PTC fallback, dynamic preset/tool loading, creative lab, dsh-go screen control
★ 10+ · lishize20040802-rgb/dsh-deep-ptc-mode source on GitHub · this plugin in the registry
lishize20040802-rgb/dsh-deep-ptc-mode is a DeepSeek Harness plugin rated C2 — one powerful capability or sensitive behavior. It patches the dsh runtime, can rewrite the system prompt, command execution in build output only.
Installable plugin — declares a dsh.bundle manifest
What it can do
| Capability | Flag | Evidence |
|---|---|---|
| patches the dsh runtime | runtime_patch | ./cordis.patch.yml |
| can rewrite the system prompt | prompt_surface | systemPrompt, system-prompt/assemble |
| command execution in build output only | exec_bundled | ×3 in build output only, e.g. lib/index.mjs:3, lib/index.mjs:3 |
Tool registrations
0 confirmed registration point(s); analysis is incomplete.
lib/tool-compatibility.mjs:43Cannot establish the tools service binding
Services it injects
agentPresets configForms locale slots systemPrompt tools
Hooks it attaches
agent/inbox/inserted loader/volatile-update system-prompt/assemble tools/execute tools/result
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.