Security audit
Security checks for vulnerabilities and agentic risk
The skill needs review because it allows payment checkout creation without confirming the details and executes an unverified installer during setup.
Require confirmation of checkout details before initialization. Review and verify the CLI installer separately, and review or disable its automatic skill synchronization. OOMOL will mediate access to your connected Paystack data. The remote installer and connector implementation were unavailable for inspection; no malicious behavior was established.
The visible code performs remote software installation rather than interacting with Paystack. Although installation can be a supporting implementation detail, the supplied chunk establishes no relationship between this installer and the declared purpose. The remote script's contents are unavailable, so its additional behavior cannot be determined.
Piping a remotely fetched installer directly into bash executes mutable network content with the invoking user's privileges, without a pinned version or independent integrity verification. The legitimate dependency relationship and missing-CLI prerequisite reduce suspicion of malicious intent, but a compromised distribution endpoint could still enable local code execution; the PowerShell alternative has the same weakness.
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 initialize_transaction action creates a payment transaction and checkout details but lacks a write tag, causing the safety instructions to classify it as a read that can run without confirmation. This can create unintended payment state using unconfirmed transaction parameters, although initialization alone does not establish that a customer is charged.
The blanket rule that untagged actions are reads makes missing annotations fail open, allowing transaction initialization to bypass the intended confirmation boundary. This is the same underlying vulnerability as SDI-4, not an additional independent impact.
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