Security audit
Security checks for vulnerabilities and agentic risk
The analytics workflow is coherent, but its setup directs the agent to run unverified downloaded software without asking you first.
Review and approve CLI installation separately before allowing the setup fallback. Check the downloaded installer and the CLI's automatic skill-installation behavior; the remote installer contents remain unverified. Connecting Simple Analytics authorizes OOMOL to mediate account access. Retain the skill's explicit confirmation requirements for writes.
The supplied command executes an installer hosted by Oomol, not Simple Analytics. Nothing in the provided chunk establishes that this installation supports the declared analytics functionality. The remote script's contents are not provided, so its additional behavior cannot be assessed.
The command pipes a mutable HTTPS response directly into Bash without version pinning or independent integrity verification. Compromise of the installer distribution path could execute attacker-controlled code with the invoking user's permissions, exposing local files and credentials; the legitimate dependency relationship and conditional setup reduce suspicion of malicious intent but do not eliminate this supply-chain risk.
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 directs installation through remote shell or PowerShell execution without explicitly obtaining approval for local system changes or explaining the execution risk. Its missing-CLI condition limits exposure, but an analytics request could still lead to unreviewed code running with the invoking user's permissions; the declared tool allowlist may restrict execution but does not make these instructions safe.
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