Security audit
Security checks for vulnerabilities and agentic risk
Segment changes require approval, but the helper software can execute unverified online code and install persistent instructions in other agent applications.
Review before installing. Use a separately reviewed CLI installation, understand that Segment payloads pass through OOMOL, and retain confirmation for every write. Disable startup skill synchronization before invoking oo if you do not want additional agent instructions installed; the publisher documents OO_SKILLS_SYNC_DISABLED=1 in its [command reference](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md#environment-variables). The bundled file was fully inspected, but the remote installers and deployed services remain unverified.
The supplied command performs remote software installation rather than the declared Segment data operations. Nothing in the code establishes that this installation supports Segment functionality, so it is not justified as a supporting implementation detail. The downloaded script's contents and any further behavior cannot be determined from this chunk.
The setup instruction pipes a mutable remote script directly into Bash without verifying its integrity or authenticity beyond HTTPS; the PowerShell alternative has the same weakness. If the distribution endpoint or delivery pipeline is compromised, following this fallback could execute attacker-controlled code with the agent's local permissions, potentially exposing accessible files and credentials. Its restriction to a missing-CLI error reduces exposure but does not remove the 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
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