Security audit
Security checks for vulnerabilities and agentic risk
The Nasdaq workflow fits its stated purpose, but fallback setup runs unverified remote installers without clear user approval or disclosure of persistent agent changes.
Review the setup before enabling this skill. Install a verified, pinned oo release under your control and review or disable bundled-skill synchronization. OOMOL brokers authenticated requests and may charge credits. The supplied workflow shows no malicious intent, but the remote installers and hosted connector implementation were not inspected.
The supplied code performs remote script execution from cli.oomol.com and contains no Nasdaq Data Link functionality. Nothing supplied establishes that this installation is a supporting dependency for the declared purpose. The downloaded script's contents and further effects cannot be determined from this chunk.
The only supplied behavior is a login operation, rather than the declared Nasdaq Data Link functionality. Authentication could be a supporting implementation detail if tied to that service, but the chunk provides no such connection. The identity of oo and the authentication destination cannot be determined from the supplied code.
Piping a live HTTPS response directly into bash executes mutable remote code without a pinned version, integrity verification, or review; the PowerShell alternative has the same weakness. Compromise of the distribution endpoint or delivery pipeline could execute attacker-controlled code with the agent process's permissions, potentially exposing local credentials and files. The documented vendor relationship makes legitimate setup plausible 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
A missing dependency triggers instructions to execute a remote installer without first obtaining approval for local software installation. This crosses from a read-only data request into local code execution and system modification; the failure-only condition reduces exposure but does not authorize those effects.
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