MengYuil/dsh-ponytail
C2Lazy senior dev mode for DeepSeek Harness — ponytail port (always-on minimal-code ruleset, /ponytail-review/audit/debt/gain/help)
★ 10+ · MengYuil/dsh-ponytail source on GitHub · this plugin in the registry
MengYuil/dsh-ponytail 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, executes commands in development tooling the package does not ship.
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 |
| command execution in build output only | exec_bundled | ×4 in build output only, e.g. scripts/lib/run-command.mjs:27, scripts/lib/run-command.mjs:27 |
| executes commands in development tooling the package does not ship | exec_tooling | ×13 in development tooling the package does not ship, e.g. scripts/check-release-consistency.mjs:30, scripts/check-release-consistency.mjs:30 |
Services it injects
invariants skills systemPrompt
Hooks it attaches
agent/disposed agent/pre-step
Environment variables it reads
PONYTAIL_SUBAGENT_MATCHER npm_execpath PONYTAIL_VERIFY_KEEP_TEMP
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.