unity-cli

SUSPICIOUS: the skill’s capabilities largely match its stated Unity automation purpose, and there is no clear credential harvesting or exfiltration behavior. Risk comes mainly from `cs setup` installing/updating an in-project Unity package from a personal GitHub source and from the broad power to execute C# inside Unity; this is coherent with the purpose but carries medium supply-chain and execution trust risk.

No explicit malicious logic (hardcoded secrets, direct exfiltration, or suspicious payload/obfuscation) is visible in this wrapper fragment. The primary security concern is the dynamic execution of a local sibling module (run_routing_current.py) via exec_module, which grants that module full execution privileges and determines any subprocess/network/filesystem effects. The inclusion of git-clean and fixed-revision enforcement plus before/after stability checks is a positive integrity/reproducibility signal, but it cannot be verified without reviewing the dynamically loaded runner implementation. Review run_routing_current.py (especially validate_output_path, _run_one, load_evals, and any subprocess/network code) to confirm it cannot be abused for unsafe writes, unintended command execution, or data leakage.