Security audit
Security checks for vulnerabilities and agentic risk
The TwitterAPI.io workflow is coherent, but a missing dependency can trigger installation of unverified remote code without clear user approval.
Review and install a verified CLI release separately before allowing this skill to run, and prevent automatic installer execution. Understand that requests use your OOMOL-connected account, and retain the documented approval checks for changes and deletions. Installer contents and their persistent effects could not be verified; the supplied artifact does not establish malicious intent.
The supplied command executes an installer hosted at cli.oomol.com rather than performing TwitterAPI.io operations. Nothing in the supplied chunk establishes that this installation supports the declared purpose. The downloaded script is not supplied, so its specific actions cannot be determined.
Piping a live HTTPS response directly into bash executes mutable remote code without a pinned version or independent integrity verification. Compromise of the installer endpoint or its distribution infrastructure could therefore execute attacker-controlled commands with the invoking process's privileges; the documented dependency explains the download but does not remove 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 setup fallback directs the agent to execute a remote installer without requiring approval for local installation or explaining that downloaded code will run with the agent's privileges. Restricting setup to a missing-CLI error reduces unnecessary execution, but an ordinary API request could still lead to unapproved host changes; the declared oo-only tool allowance may constrain execution if strictly enforced.
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