vibe-any/dsh-plugin-save-token
C3A DeepSeek Harness (dsh) dynamic plugin that cuts token cost without cutting model intelligence
★ 5+ · vibe-any/dsh-plugin-save-token source on GitHub · this plugin in the registry
vibe-any/dsh-plugin-save-token is a DeepSeek Harness plugin rated C3 — powerful capability combined with sensitive behavior. It patches the dsh runtime, executes system commands, starts a network server, 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 | ×2 in authored code, e.g. codex-plugin-save-token/src/tools.js:18, codex-plugin-save-token/src/tools.js:79 |
| starts a network server | net_server | ×3 in authored code, e.g. codex-plugin-save-token/scripts/dashboard.mjs:96, codex-plugin-save-token/src/index.js:26 |
| reads credential-class env vars | token_env | SAVE_TOKEN_DEBUG, SAVE_TOKEN_SPILL_DIR |
Services it injects
locale slots tools webServer
Hooks it attaches
agent/pre-step llm/stream tools/post-execute
Environment variables it reads
CODEX_HOME SAVE_TOKEN_DEBUG SAVE_TOKEN_SPILL_DIR
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.