Security audit
Security checks for vulnerabilities and agentic risk
Review is needed because the skill directs the agent to run a remote installer without verifying it or obtaining separate installation approval.
Review and approve the CLI installation separately, using a verified release, and check or disable automatic bundled-skill synchronization. Connect only the Griptape permissions needed and retain the required confirmations for changes and deletions. All bundled artifact content was inspected, but the remote installers and hosted connector implementation were not verified. No malicious behavior was established.
The supplied code executes an Oomol installer and contains no Griptape operations or evidence that this installation supports Griptape functionality. Its resource access and apparent primary purpose therefore differ materially from the description. The downloaded script is not supplied, so its additional behavior cannot be determined.
The command pipes a mutable remote script directly into Bash without a pinned version, independent integrity verification, or review; the PowerShell alternative has the same underlying issue. If the distribution endpoint or release pipeline is compromised, attacker-controlled code executes with the agent's local privileges, potentially accessing files and credentials. HTTPS and the legitimate dependency context reduce some risks but do not establish the integrity of the delivered script.
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 directs the agent to install software after a missing-command error without requiring approval for executing remote code or modifying the local environment. Although conditional and relevant to the task, this expands a Griptape data request into local software installation; the confirmation rules for Griptape writes do not cover this action.
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