Security audit
Security checks for vulnerabilities and agentic risk
PostGrid operations have clear approval safeguards, but setup runs unverified remote code and the CLI has broader agent-skill installation effects that deserve review.
Review the CLI installation and its broader effects before enabling automatic setup. Prefer a reviewed, version-pinned installation. The publisher documents OO_SKILLS_SYNC_DISABLED=1 to prevent startup skill synchronization in its [command reference](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md#environment-variables). Connect only the intended PostGrid account and retain confirmation for every write or deletion. The remote installers and hosted credential handling were not independently verified.
The supplied code performs no visible PostGrid operations. Instead, it executes an installer from a different service. Nothing in the supplied chunk establishes this installation as a supporting dependency for PostGrid, so its visible behavior materially differs from the declared purpose. The downloaded script's contents and further effects are not provided.
The only supplied behavior is authentication through oo; it does not implement the declared PostGrid functionality. Authentication could be a supporting implementation detail, but the supplied chunk establishes no connection between this login and PostGrid.
The installation command pipes a mutable remote script directly into Bash without a pinned version, independent integrity verification, or review; the PowerShell alternative has the same problem. Compromise of the distribution endpoint could therefore execute arbitrary code with the agent process's permissions, potentially exposing local files or credentials. The missing-CLI condition limits when this occurs but does not protect execution once triggered.
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
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