dsh-download-guard

When running the aria2-download skill in DSH, the rules live in the prompt, which is only a suggestion. If an agent has a download.cjs at hand it will happily use a single-connection node download and bypass the aria2 engine entirely. The same 4.76 GB Windows image measured roughly 90x slower on the bypass path, and Motrix shows no trace of it. The problem is not unwillingness: at the shell level node download.cjs and aria2-dl.js look identical, and nothing can tell them apart.\n\nThis plugin moves the rule to runtime. It hooks into cordis tools/pre-execute waterfall and adjudicates before the tool actually runs: any command that writes bytes to disk (curl -o, wget with default output, Invoke-WebRequest -OutFile, Start-BitsTransfer, etc.) is denied outright. The denial message auto-extracts the target URL and embeds it in the correct aria2 forwarding command, so the caller never has to guess how to rewrite. The plugin ships its own aria2 JSON-RPC forwarder that talks to the aria2-next engine without requiring aria2c.exe locally.\n\nIdeal for developers who run DSH with Motrix Next and the aria2-download skill, and want stable download speeds with full visibility in the Motrix panel. Detection rules are deliberately biased toward false negatives over false positives: pip install, npm install, git clone, pure API calls, and commands inside comments all pass through unaffected, so there is no visible regression in daily workflows.