Security audit
Security checks for vulnerabilities and agentic risk
The Workast workflow requires approval for data changes, but its setup fallback runs unverified installation scripts without a separate approval step.
Before enabling the setup fallback, review and explicitly approve the CLI installation, including its automatic skill installation and synchronization. Prefer a reviewed, pinned release. Decide whether you trust OOMOL with Workast access, and retain confirmation for every write. The remote installers and hosted connector implementation could not be verified.
The supplied chunk performs remote installer execution rather than any demonstrated Workast operation. No evidence establishes this installer as a supporting dependency for Workast, making its purpose and resource access inconsistent with the description. The downloaded script's contents and resulting actions are not available for assessment.
Piping a remotely fetched script directly into bash executes mutable network content with the agent process's privileges, without independent integrity verification or review. Compromise of the distribution endpoint could therefore expose local files and credentials or modify the host; the adjacent PowerShell command has the same risk. The legitimate dependency-setup context and missing-CLI condition narrow exposure but do 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 fallback directs the agent to install software without requiring informed user approval for local system changes. The Workast write-confirmation rules do not cover software installation, so a routine Workast request could trigger an unexpected installation if execution permissions allow it.
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