Security audit
Security checks for vulnerabilities and agentic risk
The Smartsheet workflow is sensible, but its setup can execute unverified downloaded code and introduce broader changes to your agent tools without clear approval.
Review and approve CLI installation separately, using a pinned and verified distribution. Decide whether OOMOL may install or synchronize skills across your agent tools, and disable that behavior if unwanted. Connecting Smartsheet entrusts OOMOL with account access and sheet operations; limit that access and retain the documented approval steps for changes and deletions. The downloaded installers remain unreviewed.
The supplied chunk performs remote software installation rather than Smartsheet operations. Although installation can be a supporting implementation detail, this code provides no evidence that the Oomol installer supports the declared Smartsheet functionality. The remote script's contents and any further effects cannot be determined from this chunk.
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
- `add_rows` — Add one or more rows to a Smartsheet sheet. [write]
- `delete_rows` — Delete one or more rows from a Smartsheet sheet. [destructive]
- `get_sheet` — Get a Smartsheet sheet with columns and rows.
- `list_sheets` — List sheets available to the authenticated Smartsheet access token.
- `update_rows` — Update one or more rows in a Smartsheet sheet. [write]
## Safety
Piping a mutable HTTPS installer directly into bash executes whatever the endpoint supplies without verifying a specific release or reviewing the downloaded content. A compromised distribution endpoint could execute arbitrary code and access local files or credentials; the legitimate dependency purpose and missing-CLI condition reduce exposure but do not eliminate 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 execute downloaded shell or PowerShell code without explicit installation approval or integrity verification. Although conditional on a missing CLI and relevant to the workflow, installation can execute arbitrary code with the agent's local privileges, exceeding ordinary Smartsheet operations.
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