Security audit
Security checks for vulnerabilities and agentic risk
The Parallel integration is coherent, but its setup can make broader local changes than the skill explains or asks you to approve.
Review setup before installing. Use a separately reviewed CLI version and disable automatic skill synchronization unless you want additional agent skills installed. Confirm that sending task data through OOMOL is acceptable. Parallel writes have explicit approval safeguards, but the downloaded installers and live connector implementation were unavailable for verification.
The supplied command executes an installer from cli.oomol.com, with no visible connection to Parallel or its data operations. Although dependency installation can be a supporting implementation detail, this chunk provides no evidence that the Oomol installer supports the declared purpose. The downloaded script is not supplied, so its additional behavior cannot be determined.
Piping a remotely fetched script directly into Bash executes whatever the endpoint supplies with the invoking user's privileges, without a pinned version or independent integrity verification. Although this is a documented dependency installation rather than evidence of malicious intent, compromise of the distribution endpoint or release process could expose local files and credentials or enable persistent changes; the PowerShell alternative has the same underlying risk.
oo: command not found — install the oo CLI (other platforms: https://cli.oomol.com/install-guide.md):
curl -fsSL https://cli.oomol.com/install.sh | bash # macOS / Linux
The missing-CLI fallback directs the agent to execute remote installation scripts without explicitly requesting approval for local code execution or system changes. Limiting this to a setup failure reduces exposure, but a request to operate Parallel does not necessarily authorize installing software on the user's machine.
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
- **`OOMOL_INSUFFICIENT_CREDIT`** — OOMOL billing stop. Recharge at `https://console.oomol.com/billing/token-recharge` before retrying.
- **HTTP 402 without `OOMOL_INSUFFICIENT_CREDIT`** — the third-party account itself has no active plan or credit. Report the provider error message as is; do not ask the user to recharge OOMOL.
## Resources