Security audit
Security checks for vulnerabilities and agentic risk
The Fireberry workflow requires approval for data changes, but setup can execute unverified remote code without separate installation approval.
Review the setup before use. Install a verified CLI yourself rather than allowing automatic remote-script execution. OOMOL will mediate access to your Fireberry data; connect only needed permissions and approve exact changes or deletions. The sole bundled artifact was fully inspected, but remote installer and connector behavior remain unverified.
The supplied chunk performs remote installer execution, not Fireberry data management. Although installation can be a supporting implementation detail, nothing in this chunk establishes that this installer supports Fireberry. The remote script's contents are not supplied, so its further behavior cannot be assessed.
Piping an HTTPS response directly into bash executes mutable remote content without verifying or reviewing it. Although the endpoint is consistent with the documented CLI provider and installation is conditional, compromise of the hosting infrastructure or release pipeline could allow code execution and access to local data with the agent's privileges.
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 setup directs the agent to execute remotely supplied shell or PowerShell code without review, integrity verification, or explicit approval for local installation. The missing-CLI condition limits exposure, but a compromised installer source could execute arbitrary code with the invoking user's privileges; this overlaps with SC2.
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