Security audit
Security checks for vulnerabilities and agentic risk
The Drimify reads match the stated purpose, but its helper can install persistent skills into other agents without the skill explaining those broader changes.
Review the helper's persistent changes before allowing setup. Use a separately verified CLI installation and disable startup skill synchronization with OO_SKILLS_SYNC_DISABLED=1 if additional agent skills are unwanted. OOMOL mediates the Drimify connection. The installer contents and deployed connector implementation were not verified; the bundled-file coverage exceptions were resolved by direct inspection.
The supplied command performs remote script execution rather than searching or reading Drimify data. Nothing in the chunk establishes that installing the Oomol CLI is a supporting dependency for Drimify access. The script's downstream actions are not visible, but downloading and executing this unrelated installer is itself outside the declared purpose.
Piping the HTTPS response directly into Bash executes mutable remote content without prior inspection or artifact verification. HTTPS protects transport but does not prevent a compromised publisher or distribution endpoint from supplying malicious code; this is the same underlying installer risk identified by SQP-2, not an independent exploit.
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 execute downloaded shell or PowerShell code immediately, without an explicit installation approval step or artifact-integrity verification. A compromised installer source could execute arbitrary code with the invoking user's privileges; restricting setup to a missing-CLI error reduces exposure but does not remove this risk.
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