Security audit
Security checks for vulnerabilities and agentic risk
Review is recommended because setup executes unpinned remote code and the required CLI can automatically install additional persistent agent skills.
Review and verify the CLI installation before allowing setup. Consider disabling startup skill synchronization using the publisher-documented OO_SKILLS_SYNC_DISABLED setting. Understand that OOMOL mediates Plunk access, and retain the skill's confirmation requirements for email, contact changes, and deletion. The remote installer and hosted service remain outside the inspected artifact.
The supplied command installs software from Oomol rather than performing the declared Plunk operations. Nothing in the supplied code establishes this installation as a supporting dependency for Plunk. The remote script's contents are not supplied, so its further 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. A compromised distribution endpoint could therefore compromise the local environment; the missing-CLI prerequisite reduces exposure but does not remove this supply-chain risk, and the PowerShell example has the same weakness.
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
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