Security audit
Security checks for vulnerabilities and agentic risk
The Bloomerang actions are read-only, but setup needs review because it executes unverified downloads and may introduce additional persistent agent skills.
Review and approve CLI installation separately, using an inspected, pinned release. Confirm that OOMOL may handle your constituent data and grant only necessary account access. Upstream documents OO_SKILLS_SYNC_DISABLED=1 to prevent startup skill synchronization in its [command reference](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md). Only Markdown was bundled; remote installer and service behavior remain unverified.
The supplied chunk installs or bootstraps external software through remote shell execution, while the description promises Bloomerang data access. Nothing in the supplied code establishes that this installer is a supporting dependency for Bloomerang functionality. The downloaded script's contents and further effects are not available for assessment.
Piping an HTTPS response directly into Bash executes mutable remote content without establishing a trusted version or verifying its integrity independently. If the distribution endpoint or release pipeline is compromised, a routine read-only Bloomerang task could trigger local code execution, potentially exposing files or credentials accessible to the process.
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 setup instructions execute remotely supplied shell or PowerShell code without a separate verification or approval step. Although installation is conditional on a missing CLI, compromise of the installer source could cause arbitrary code execution with the invoking user's privileges; this overlaps with SC2 rather than representing an independent exploit.
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