Security audit
Security checks for vulnerabilities and agentic risk
The Google Forms workflow has clear safeguards, but setup can execute unverified software whose documented behavior includes installing additional persistent agent skills.
Review and approve the CLI installation separately. Consider disabling automatic skill synchronization before running it; the [command reference](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md) documents OO_SKILLS_SYNC_DISABLED. Connect only the Google Forms permissions you need and retain confirmation for changes. Installer contents and hosted connector behavior remain unverified.
The supplied chunk performs remote script execution rather than any visible Google Forms operation. Installation can be a supporting implementation detail, but this chunk establishes no relationship between the Oomol installer and the declared Google Forms functionality. The remote script's contents and any further effects cannot be determined from the supplied code.
Piping a mutable remote installer directly into bash gives the fetched content code-execution privileges without an integrity check or review opportunity. HTTPS protects transport but does not protect against a compromised distribution server or malicious installer update; this is the same underlying installation 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 workflow instructs immediate execution of remotely retrieved shell and PowerShell scripts without verifying their contents or obtaining explicit approval for local software installation. Setup is conditional on a missing CLI, which limits exposure, but a compromised installer source could still execute arbitrary code with the invoking user's 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