Security audit
Security checks for vulnerabilities and agentic risk
The Planhat workflow has clear safeguards, but its automatic setup can execute unverified remote installers without approval for their local effects.
Review and approve CLI installation separately, preferably using a pinned, verified release. Check whether it installs or updates other agent skills. OOMOL mediates Planhat access, and changes to Planhat records should follow the skill's explicit confirmation rules. The remote installers were unavailable for inspection, so their exact local effects remain uncertain.
The supplied chunk performs remote installer execution rather than any visible Planhat operation. Dependency installation can be a supporting implementation detail, but this chunk establishes no relationship between the Oomol installer and the declared Planhat functionality. The downloaded script is not supplied, so its subsequent behavior and any Planhat integration cannot be verified.
The curl-to-Bash pipeline executes mutable remote content without a pinned version or independent integrity verification. Compromise of the installer distribution path could execute attacker-controlled code with the agent's local privileges; HTTPS and the legitimate CLI dependency reduce neither that supply-chain consequence nor the need for verification.
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 directs execution of downloaded Bash or PowerShell scripts without explaining their local effects or requiring explicit approval for installing software. Although this occurs only when the CLI is missing, a routine Planhat request could consequently lead to local code execution with the agent's privileges rather than just connector operations.
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