image-to-threejs

SUSPICIOUS. The skill's capabilities broadly match its stated purpose, and data stays local aside from expected GitHub/package downloads. The main concern is install/execution trust: it requires cloning and running a third-party GitHub toolchain plus Playwright/browser components outside an official package release flow. This looks like a coherent but high-trust developer workflow rather than confirmed malware.

This module appears to be benign image-processing logic (threshold-based foreground detection, bbox calculation, cropping/resizing, and sidecar metadata generation). However, it includes a significant supply-chain/local code execution risk: it prepends a CLI-controlled directory to sys.path and imports extract_pbr_evidence from there, which will execute any import-time code contained in that directory. If the --i2t path (or ~/.local/share/img2threejs by default) can be influenced or replaced by an attacker, arbitrary code execution is possible. Otherwise, the remaining operations are straightforward and non-malicious.