Security audit
Security checks for vulnerabilities and agentic risk
This skill needs review because its setup executes unverified remote code and omits broader changes the CLI can make to installed agent skills.
Review and install the CLI separately before allowing automatic setup. OOMOL will handle the connected account and Process Street requests. Consider disabling startup skill synchronization with OO_SKILLS_SYNC_DISABLED=1, as documented in the [publisher's reference](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md). Retain the required confirmations for writes. This review does not establish the safety of the unavailable remote installer.
The supplied code performs remote script execution rather than any visible Process Street operation. Although dependency installation can be a supporting implementation detail, this chunk provides no evidence that the Oomol installer supports the declared Process Street functionality. The downloaded script's contents and subsequent behavior are not available for assessment.
Piping the HTTPS response directly into bash executes mutable remote code without version pinning, signature verification, or a review step. A compromised installation endpoint or release infrastructure could execute arbitrary commands with the invoking user's privileges; 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 fallback setup directs the agent to execute remotely supplied installation code without requiring explicit approval for local system changes or explaining the execution risk. Limiting setup to a missing CLI reduces exposure, but installing software is a separate trust boundary from operating Process Street and can affect the local machine with the agent's permissions.
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