pcp-setup

The fragment describes a legitimate-looking helper to install PCP components by downloading a plugin and skills from a public GitHub source and wiring them into the OpenCode configuration. While the described behavior is coherent with the stated purpose, the approach lacks integrity verification (no checksums or signatures) and relies on remote content being trustworthy. This creates a potential supply-chain risk: if the remote artifacts are compromised, a malicious plugin or skill could be installed and loaded by OpenCode. The overall risk is moderate (suspicious-but-not-executable malware) given the absence of verification steps, with a higher risk if the downloaded plugin/skills auto-execute upon OpenCode startup. Recommend adding: strict version pinning, cryptographic verification (SHA256/PGP), and a manifest/signature verification step before installation. Also consider pinning to a known-good release URL and providing a rollback path.