Security audit
Security checks for vulnerabilities and agentic risk
The L2S actions have clear safeguards, but setup executes unverified downloaded code and leaves broader changes to agent skills undisclosed.
Review and approve dependency installation separately, preferably using a pinned release with verified integrity. Expect L2S data to pass through OOMOL. Before invoking the CLI, review its automatic skill synchronization; current documentation provides OO_SKILLS_SYNC_DISABLED=1 to disable startup skill writes. The live installers were unavailable for inspection, so their exact system changes remain uncertain.
The visible behavior installs software from Oomol rather than accessing L2S. Nothing in the supplied description or code establishes this installer as a supporting dependency for L2S, so it represents an undeclared capability and inconsistent resource access. The downloaded script's contents and further effects cannot be determined from this chunk.
The command downloads a mutable remote script and immediately executes it without inspection, version pinning, or independent integrity verification; the PowerShell alternative follows the same pattern. If the distribution endpoint or release pipeline is compromised, attacker-controlled code could run with the invoking user's privileges and access local data or credentials. The legitimate dependency context and HTTPS reduce suspicion of malicious intent but do not eliminate this supply-chain 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 setup instructions direct the agent to install software after a command-not-found error without requiring approval for local code execution or explaining potential system changes. Restricting installation to first-time setup reduces exposure, but the write-confirmation rules only cover L2S actions and do not explicitly protect this local installation step.
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