Security audit
Security checks for vulnerabilities and agentic risk
Review is needed because a missing prerequisite can trigger downloaded installer code without a clear user approval step.
Review and approve CLI installation separately, verify the release, and check its automatic skill synchronization before allowing setup. Connect only the intended QuintaDB account and confirm every write or deletion. OOMOL mediates database access; installer contents and hosted connector implementation were not verified.
The supplied code executes an Oomol CLI installer rather than performing QuintaDB operations. No connection between this installation and the declared QuintaDB functionality is established. The downloaded script is not supplied, so its additional behavior cannot be assessed.
The command pipes an unpinned HTTPS response directly into bash, allowing the installation endpoint to supply code that executes with the invoking process's privileges. Compromise of the endpoint or its delivery infrastructure could expose local files and credentials or enable persistent changes; HTTPS alone does not establish the integrity of the script. This is a legitimate prerequisite-installation context, not evidence of malicious intent, and it overlaps with SQP-2.
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 installation through remotely downloaded shell or PowerShell scripts without requiring user approval or explaining that arbitrary code will run locally. A request to operate QuintaDB could therefore trigger local software installation with the agent's privileges; the missing-CLI condition limits exposure but does not establish consent 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