Security audit
Security checks for vulnerabilities and agentic risk
This skill can start paid audio processing without confirmation, and its setup has broader effects on agent skills than it explains.
Require confirmation before vocal separation and other generating or processing actions; review style boosting, which is also untagged. Preinstall a reviewed CLI release and decide whether to permit its automatic skill synchronization. OOMOL mediates account access and submitted content. The remote installers and hosted connector code were not verified, so their full runtime effects remain uncertain.
The supplied command executes a remote installer, while the description promises SunoAPI functionality. Nothing in the supplied chunk establishes that this installer is a supporting dependency for SunoAPI. The installer contents are not provided, so its downstream behavior cannot be determined.
The supplied code only invokes an oo login operation and shows no connection to SunoAPI. Authentication could be a supporting implementation detail if oo were established as part of the SunoAPI integration, but that relationship is not present in the supplied material.
The fallback installation command downloads a mutable remote script and immediately executes it without version pinning or independent integrity verification; the PowerShell alternative has the same weakness. If the distribution endpoint or release infrastructure is compromised, attacker-controlled code could run with the agent's local privileges and access local files or credentials. Its conditional use and HTTPS transport reduce exposure but do not establish script integrity.
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 skill describes separate_vocals_from_music as submitting a task but leaves it untagged, while explicitly authorizing untagged actions to run directly as reads. This bypasses the skill's confirmation requirement for state-changing operations and could initiate unwanted processing or consume account credits.
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