Security audit
Security checks for vulnerabilities and agentic risk
The Firstbase features fit the stated purpose, but setup and the linked CLI can make broader local changes that the skill does not explain.
Review and install a verified CLI release yourself before allowing this skill to run. Consider setting OO_SKILLS_SYNC_DISABLED=1 before invoking it to prevent automatic changes to agent skill directories. Connect only the intended Firstbase account with read access, and understand that OOMOL intermediates requests. The review concerns installation control and under-disclosed persistent changes; the inspected artifact does not establish malicious intent.
The supplied command performs no visible Firstbase search or read operation. Instead, it fetches and executes an external installer. Nothing in the supplied content establishes this installation as a supporting implementation detail for Firstbase access. The fetched script's further behavior cannot be determined from this chunk.
The command pipes a remotely fetched, mutable script directly into Bash without version pinning or independent integrity verification. Compromise of the installer hosting or delivery infrastructure could therefore yield code execution with the agent's local privileges; HTTPS and a relevant vendor domain do not eliminate that 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
A missing CLI triggers instructions to execute a downloaded installer without first obtaining approval for local software installation. Both the shell and PowerShell variants can execute arbitrary code with the invoking user's privileges; the missing-dependency condition limits exposure but does not establish user authorization for those changes.
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