Security audit
Security checks for vulnerabilities and agentic risk
The ShipBob workflow fits its purpose, but setup directs the agent to execute unchecked remote installers without an explicit approval step.
Review before installing. Use a separately reviewed CLI release and explicitly approve local installation changes. Check its automatic skill-installation settings and confirm that OOMOL may access your ShipBob data. The installer and server-side connector implementation are outside the inspected bundle; no malicious behavior was established.
The supplied chunk runs an Oomol installation script rather than accessing ShipBob data. Dependency installation could be a supporting implementation detail, but the supplied content establishes no relationship between this installer and the declared ShipBob functionality. The downloaded script's contents and further effects are not shown.
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
## Available actions
- `get_inventory_level` — Get aggregated ShipBob inventory levels for one inventory item.
- `list_channels` — List ShipBob channels available to the authenticated Personal Access Token.
- `list_inventory_levels` — List ShipBob inventory levels with optional item and product filters.
- `list_locations` — List ShipBob fulfillment network locations.
- `list_products` — List ShipBob products with optional catalog filters.
Piping an unpinned remote script directly into bash executes whatever the endpoint supplies with the invoking user's privileges, without an independent integrity check or review opportunity. HTTPS protects transport but not against a compromised distribution endpoint or malicious release; the PowerShell fallback uses the same download-and-execute pattern. The setup-only condition reduces exposure, and enforced tool restrictions might block execution, but neither makes the prescribed mechanism safe.
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 fallback directs the agent to install software after a missing-command error without first explaining local system changes or obtaining approval. A request to read ShipBob data does not itself authorize installing software, although the conditional fallback limits when this exposure occurs.
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