Security audit
Security checks for vulnerabilities and agentic risk
The Printavo functions fit the stated purpose, but setup can execute unverified software and introduce broader changes to your agent’s skills.
Review the CLI setup before enabling this skill. Install a verified version yourself and confirm that OOMOL may process your Printavo business data. The installer contents were unavailable for inspection. Before running oo, consider disabling its broader skill synchronization with OO_SKILLS_SYNC_DISABLED=1, as described in the [publisher’s command reference](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md#environment-variables). No malicious intent was established.
The declared purpose concerns accessing Printavo data, while the supplied code executes an installer from a different service. No evidence in the chunk establishes this installation as a supporting requirement for Printavo access. The downloaded script is not supplied, so its exact actions and system changes cannot be determined.
The curl-to-bash pipeline executes whatever script the remote endpoint returns, without an opportunity to verify the complete artifact before execution. HTTPS protects transport but does not protect against compromise of the distribution infrastructure or malicious changes to the installer. The legitimate CLI dependency and conditional setup reduce suspicion of malicious intent, not the potential impact.
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
Both setup commands execute remotely retrieved code immediately, without a pinned artifact or independent integrity verification. A compromised installer source could execute arbitrary code with the invoking user's permissions; the missing-command condition limits exposure but does not make installation safe. This overlaps with SC2 rather than representing a separate exploit.
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