plannotator

The script is a typical installer wrapper with optional integration setup. The major security concern is the remote installer execution via curl | bash, which can run unverified code from an external source. This is a high-risk pattern (source-to-sink path) and should be mitigated by using verified installers, checksums/signatures, or downloading to a file and running with explicit verification. Otherwise, the script itself contains no overt malicious behavior, but relies on external remote code that could compromise the system if the remote source is compromised.

The plannotator skill is conceptually aligned with a plan/diff review tool with extensible integrations and local note-saving. However, the install/initialization footprint depends on downloading and executing code from an external domain (plannotator.ai), which constitutes a notable supply-chain risk. Data flows to local vaults (Obsidian/Bear) are appropriate for the stated purpose when properly sandboxed, but remote/hook-based configurations and multiple CLI integrations amplify risk if any configuration is downloaded or executed without verification. Overall, the footprint is moderately suspicious due to the download-execute pattern and unverifiable external install source; I would classify this as SUSPICIOUS with elevated securityRisk until verifiable checksums, signed releases, or a vetted registry distribution are provided.