Security audit
Security checks for vulnerabilities and agentic risk
The data-reading functions fit the stated purpose, but setup can execute unverified remote code and introduce changes to other agent skills.
Review and install a verified CLI release yourself before enabling the skill, and require approval for any installation fallback. Check the CLI's automatic skill synchronization; its documented OO_SKILLS_SYNC_DISABLED control can prevent those writes. Intrinio requests use your OOMOL-connected account and may consume service credits. The remote installer payloads were unavailable for inspection, so their complete installation effects remain uncertain.
The supplied chunk contains only a remote installer command and shows no Intrinio interaction. Although dependency installation can be a supporting implementation detail, this chunk establishes no relationship between the Oomol installer and the declared Intrinio functionality. The downloaded script's further behavior cannot be determined from the supplied code.
Piping a remotely downloaded script directly into Bash executes mutable external content without version pinning or independent integrity verification. Compromise of the installer distribution path could execute arbitrary code with the agent's permissions; HTTPS and the legitimate OOMOL setup context reduce suspicion but do 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
The fallback instructs the agent to install software without first obtaining explicit approval for executing remote code and modifying the local environment. Although triggered only when the CLI is missing, a routine data-reading request can thereby expand into code execution with the agent's local permissions.
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