Security audit
Security checks for vulnerabilities and agentic risk
Railway actions require approval, but the CLI dependency can install additional agent skills without that broader effect being explained.
Review CLI setup separately and use narrowly scoped Railway credentials with OOMOL. Before running oo, consider setting OO_SKILLS_SYNC_DISABLED=1 to prevent automatic skill installation, as documented in the [CLI reference](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md). The remote installers and hosted backend were not verified; the Review verdict concerns installation control and undisclosed agent-environment changes.
The supplied code installs software from an Oomol endpoint and contains no Railway operations. Nothing in the chunk establishes this installation as a supporting dependency for Railway. The downloaded script's contents and further effects are not available for assessment.
Piping a mutable remote installer directly into Bash executes whatever the endpoint returns without prior verification. HTTPS reduces transport interception risk but does not protect against compromise of the vendor's hosting or release pipeline; this is the same underlying installation risk identified in SQP-2, not an independent exploit.
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 directs the agent to install software by immediately executing downloaded shell or PowerShell content, without an explicit installation approval step or an independent integrity check. Although this is a legitimate dependency and only runs when the CLI is missing, a compromised installer source could execute arbitrary code with the invoking user'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