Security audit
Security checks for vulnerabilities and agentic risk
The Tinybird workflow is coherent, but its fallback tells your agent to run an unverified remote installer without asking first.
Review and approve CLI installation separately before letting the agent use this skill. Prefer a pinned, verified release and check whether setup adds or updates other agent skills. Connect Tinybird with only the read permissions needed, and understand that requests pass through OOMOL. The remote installer and live connector implementation were not verified.
The supplied code performs remote installer execution and contains no visible Tinybird search or read functionality. Nothing in the supplied material establishes this installer as a supporting dependency for Tinybird access. The downloaded script's contents are unavailable, so its further behavior cannot be determined.
The supplied chunk only invokes an authentication command; it contains no Tinybird search, read, or integration behavior. Authentication could be a supporting implementation detail if the CLI were established as part of the Tinybird workflow, but the supplied content provides no such connection.
The command pipes a mutable remote script directly into Bash without independently verifying its integrity or reviewing it; the PowerShell alternative has the same execution pattern. If the distribution endpoint or publishing pipeline is compromised, attacker-controlled code executes with the agent process's local permissions, potentially exposing files and credentials. HTTPS and the legitimate dependency context reduce some risks but do not establish the script's integrity.
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 CLI triggers instructions to install software locally without first obtaining approval for the system changes. A request to read Tinybird data does not inherently authorize executing an installer; the error-triggered fallback limits exposure but still crosses that authorization boundary.
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