goal-mode

Not overtly malicious (no obvious backdoor/exfiltration/persistence), but it is inherently high-risk as a supply-chain execution gadget: it parses commands from a local .cursor/goal.config.yml and executes them verbatim via execSync(..., shell:true) with a workspace-derived cwd. If an attacker can influence the config content or the working directory, this module enables arbitrary command execution in the user/CI context, and it can leak command output via printed output_tail.

No clear evidence of overt malware in this module (no network access, file writes, persistence, or explicit credential theft). The primary security concern is command execution: the file uses execSync with shell-string command interpolation that incorporates `config.active_goal` into the executed shell command. If `active_goal` (directly or indirectly via configuration tampering) is attacker-controlled or not strictly sanitized, this can lead to command injection. Additionally, executing helper scripts from a relative `.cursor/skills/...` path increases impact if those files are compromised.