Security audit
Security checks for vulnerabilities and agentic risk
Paymo changes require approval, but the missing-software fallback executes remote installers without clearly obtaining permission for broader local changes.
Review and install oo yourself before enabling this skill, and check its automatic agent-skill installation settings. Keep the required approvals for Paymo changes and deletions. OOMOL handles the connected Paymo credentials and request data. The remote installers and server-side connector implementation were unavailable for verification.
The visible behavior is remote installer execution rather than Paymo data management. Although dependency installation can be a supporting implementation detail, the supplied chunk establishes no relationship between this installer and Paymo functionality. The downloaded script's contents and further effects are not available for assessment.
Piping a remotely fetched, unpinned installer directly into bash executes its contents with the invoking user's privileges, without an integrity check or review opportunity. Compromise of the distribution endpoint could therefore lead to local code execution and access to user-readable secrets; HTTPS and the legitimate dependency relationship do not eliminate this supply-chain risk. The PowerShell fallback has the same underlying issue.
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-command fallback instructs the agent to install software without first explaining the local changes or obtaining explicit installation approval. Although this is a legitimate dependency and the fallback is conditional, authorizing a Paymo task does not necessarily authorize executing an installer that can modify the local environment.
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