Security audit
Security checks for vulnerabilities and agentic risk
The Rewiser actions require confirmation, but the CLI dependency can make persistent changes to other agent apps that this skill does not explain.
Review and install the CLI separately before allowing setup. Check its cross-app skill synchronization; current documentation provides OO_SKILLS_SYNC_DISABLED=1 to disable startup synchronization. Connect only the intended Rewiser account and review each transaction payload. The remote installers and server-side implementation were not verified.
The supplied command executes an Oomol installer, with no visible connection to Rewiser or its data operations. This is an undeclared capability involving an inconsistent resource, not an established supporting implementation detail. The downloaded script's contents are unavailable, so its additional behavior cannot be determined.
Piping the HTTPS response directly into bash executes mutable remote content without verifying a pinned version, signature, or checksum. HTTPS protects transport but does not prevent a compromised vendor endpoint or publishing pipeline from delivering malicious code that could access local files and credentials; this is the same underlying installation risk identified by SQP-2, not a separate exploit chain.
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 setup instructs the agent to execute downloaded shell or PowerShell code without a separate approval step or artifact verification. If the installer delivery infrastructure is compromised, attacker-controlled code could run with the invoking account's permissions; limiting setup to a missing-CLI error reduces exposure but does not eliminate this risk.
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