Security audit
Security checks for vulnerabilities and agentic risk
The TinyPNG functions fit the stated purpose, but setup can execute unchecked remote code and introduce persistent agent skills beyond TinyPNG.
Review setup before use. Prefer separately installing a verified CLI release and disabling automatic skill synchronization if unwanted. OOMOL mediates image submissions and the connected TinyPNG account. The downloaded installers remain uninspected; this review found no evidence of deliberate malicious behavior.
The supplied code executes an external Oomol installer, an undeclared system-level action with no demonstrated connection to TinyPNG. Although dependency installation can be a supporting implementation detail, this chunk provides no evidence of that relationship. The downloaded script's contents and any additional effects cannot be determined from the supplied code.
Piping an HTTPS response directly into bash executes mutable remote code without establishing its integrity or reviewing its contents. Although the endpoint is consistent with the documented CLI provider and setup is conditional, compromise of that endpoint or its release pipeline could lead to local code execution, data theft, or file modification.
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 instructions execute downloaded shell or PowerShell scripts immediately, without integrity verification, inspection, or explicit approval for installing software. A compromised distribution endpoint or altered installer could execute arbitrary code with the invoking user's permissions; the missing-CLI condition reduces exposure but does not make execution safe.
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