Security audit
Security checks for vulnerabilities and agentic risk
The YoPlanning reader fits its purpose, but setup directs the agent to run an unverified remote installer without clear user approval.
Review the setup behavior before installing. Install and verify the CLI separately instead of letting a missing-command error trigger downloaded code execution, and check which other agent skills it installs or updates. Connecting YoPlanning authorizes OOMOL to use that account's API key. The actual installer contents remain unverified.
The supplied command installs software through a remote shell script rather than searching or reading YoPlanning data. Although installation can be a supporting implementation detail, the supplied code establishes no relationship between this installer and the declared YoPlanning functionality. The script's contents are not supplied, so its exact system changes cannot be determined.
Piping an unpinned HTTPS response directly into Bash executes whatever the installation endpoint supplies with the agent process's local privileges; the PowerShell alternative has the same trust problem. Compromise of the endpoint or release pipeline could therefore enable local data theft or modification, although installation is conditional and may be blocked by the declared tool restriction.
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
On a missing-command error, the skill directs installation without first obtaining approval for executing downloaded code or changing the local environment. The error-triggered fallback limits exposure, and strict enforcement of the declared oo-only Bash permission could block installation, but the setup instructions themselves lack an authorization boundary.
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