Security audit
Security checks for vulnerabilities and agentic risk
The Postalytics features fit the stated purpose, but setup can execute unverified downloaded code without a separate user decision.
Review the CLI installation separately before allowing the missing-dependency fallback. Prefer a verified fixed release, and check whether it installs additional agent skills. Connecting Postalytics allows OOMOL to mediate access to account data. The downloaded installer and hosted connector implementation are outside the supplied artifact, so their exact effects remain unverified.
The supplied code performs no visible Postalytics search or read operation. Instead, it executes an external installer. Although installation can be a supporting implementation detail, the supplied content provides no connection between this installer and the declared functionality. The remote script's contents and any resulting changes cannot be determined from this snippet.
The command pipes a mutable remote script directly into bash without checking its contents, version, signature, or digest. HTTPS protects transport but does not prevent a compromised distribution server from supplying malicious code, which would execute with the invoking account's privileges; the conditional setup trigger reduces exposure but does not eliminate it.
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 instructs the agent to execute remotely supplied shell or PowerShell code without an explicit installation approval step or integrity verification. Although installing a missing dependency is relevant, a read-oriented Postalytics request does not itself authorize arbitrary local software installation, which could compromise files and credentials accessible to the executing account.
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