Security audit
Security checks for vulnerabilities and agentic risk
The Analytics workflow has clear safeguards, but missing-tool setup executes unverified downloaded software without a separate approval step.
Review and approve CLI installation separately, preferably using a verified release. Review its automatic agent-skill synchronization; the [command reference](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md#environment-variables) documents an opt-out. Connect only the intended Analytics account and retain confirmation before changes or deletions. External installers and hosted connector behavior remain outside this artifact review.
The supplied code performs remote installer execution rather than a Google Analytics operation. Nothing in the chunk establishes that this installation is a supporting dependency for the declared purpose. The downloaded script's contents are not supplied, so its further behavior cannot be determined.
Piping a remotely fetched installer directly into bash executes mutable network-supplied code without version pinning, integrity verification, or review; the PowerShell example has the same weakness. Compromise of the vendor's distribution infrastructure could yield arbitrary code execution with the invoking user's privileges, despite HTTPS and the legitimate dependency relationship.
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 missing-CLI fallback directs installation through downloaded shell or PowerShell scripts without requiring user approval or explaining local system changes. Although conditional setup limits exposure, a request to operate Google Analytics does not necessarily authorize executing an installer with the agent's local privileges.
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