Security audit
Security checks for vulnerabilities and agentic risk
Review is warranted because the skill directs automatic installation from a live remote script without clearly controlling or explaining its local changes.
Review and approve the CLI installation separately, using a verified release where available. Check and control its automatic agent-skill synchronization before running it. Expect Sif requests to pass through OOMOL and consume disclosed service credits. The full remote installer behavior could not be verified; the supplied artifact does not establish malicious intent.
The supplied chunk performs remote software installation rather than searching or reading Sif data. No code establishes that this installer is a supporting dependency for Sif access. The downloaded script is not supplied, so its further behavior cannot be assessed.
The command pipes a remotely fetched, unpinned script directly into Bash without inspecting or independently verifying the executable content; the PowerShell alternative uses the same execution pattern. Compromise of the installer endpoint or its publishing chain could execute attacker-controlled code with the agent's local permissions, potentially exposing accessible credentials or modifying files. HTTPS and the legitimate dependency relationship do not protect against a compromised publisher.
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
When the CLI is missing, the fallback directs the agent to install software without first explaining local system changes or obtaining explicit approval. A request to read Sif data does not inherently authorize running an installer, which can modify files and configuration under the agent's operating-system account; the conditional fallback limits exposure but does not establish consent.
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