Security audit
Security checks for vulnerabilities and agentic risk
The Payrexx operations have confirmation safeguards, but setup directs the agent to run unverified remote installers without a separate approval step.
Review and verify the CLI installation separately before using this skill. OOMOL will mediate access to your connected Payrexx account. Check the CLI's automatic skill synchronization settings and disable that behavior if unwanted; the publisher documents OO_SKILLS_SYNC_DISABLED in its [command reference](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md). Continue requiring confirmation for checkout creation. The external installer and connector were not verified by this artifact review.
The supplied command performs remote software installation rather than the declared Payrexx operations. Nothing in the supplied chunk establishes this installer as a supporting dependency for Payrexx functionality. The downloaded script is not provided, so its further behavior cannot be assessed.
The command pipes a mutable remote script directly into Bash without checking a pinned version, signature, or independently trusted digest. HTTPS protects transport but not against a compromised distribution endpoint or publisher account, which could deliver code that steals local credentials or modifies the host; the legitimate CLI dependency explains the command but does not eliminate this supply-chain risk.
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 fallback directs the agent to execute remote shell or PowerShell installation code without requiring informed user approval or artifact verification. Although this is legitimate dependency setup and only occurs when the CLI is missing, a Payrexx task does not by itself authorize arbitrary local software installation, which can modify files and execute 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