Security audit
Security checks for vulnerabilities and agentic risk
The Featurebase workflow has clear safeguards, but its fallback setup runs unverified downloaded code without a separate approval step.
Review and approve CLI installation separately, preferably using a verified release. OOMOL mediates your Featurebase requests and account connection. Check the CLI's automatic skill synchronization before first use; its [command reference](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md#environment-variables) documents OO_SKILLS_SYNC_DISABLED. Preserve the skill's write and deletion approval requirements. The downloaded installer and remote service implementation remain outside this artifact review.
The supplied code installs software by executing a remotely fetched script; it does not show any Featurebase functionality. No evidence establishes this installer as a supporting dependency for Featurebase operations. The remote script's contents and subsequent effects are not available for assessment.
The command pipes a remotely retrieved, mutable script directly into Bash without a pinned version or independent integrity verification; the PowerShell alternative follows the same execution pattern. Compromise of the distribution endpoint or installer supply chain could execute arbitrary code with the invoking account's permissions, although the domain is a relevant dependency source and installation is only a fallback.
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 setup directs the agent to execute third-party installation code without explicitly obtaining approval for local software installation and its system changes. This is conditional rather than routine behavior, and the declared Bash allowlist may restrict execution, but neither establishes informed authorization for the installation.
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