Security audit
Security checks for vulnerabilities and agentic risk
The search workflow is coherent, but its setup can execute unverified downloads and introduce broader agent changes without clear user approval.
Review and approve CLI installation separately, and disable automatic bundled-skill synchronization unless you want changes across your agent installations. Confirm the OOMOL account and possible charges. The installer payloads and hosted connector implementation remain unverified; no malicious behavior was established.
The supplied chunk contains only a remote installer command and performs no iTunes search or data retrieval. Nothing in the chunk establishes this installation as a supporting dependency for the declared purpose. The downloaded script's further behavior cannot be determined from the supplied code.
The supplied code performs a login operation and contains no iTunes Search API request or data-reading behavior. Nothing in the snippet establishes that this authentication is a supporting requirement for the declared purpose, so its observable behavior does not match the description.
The command pipes a mutable network response directly into bash without a pinned version, signature verification, or independent integrity check. Compromise of the distribution endpoint could execute attacker-controlled code with the invoking user's permissions; HTTPS alone does not protect against a compromised publisher or installer.
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 scripts without first obtaining approval for remote code execution and local system changes. Although conditional and relevant to the connector dependency, this unnecessarily expands a read-only search task into a potentially high-impact installation operation.
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