Security audit
Security checks for vulnerabilities and agentic risk
The AfterShip workflow requires approval for data changes, but its setup directs the agent to run unverified remote code without separate approval.
Review and install a trusted CLI release yourself before use, and require separate approval for installer execution. Review its automatic skill synchronization and disable it if unwanted. Using this integration requires trusting OOMOL with connected-account access; retain the stated approval checks for tracking changes and deletion. The external installer and service implementation were not verified.
The visible behavior is execution of an Oomol CLI installer, with no demonstrated connection to AfterShip functionality. Although dependency installation can be a supporting implementation detail, the supplied content establishes no such relationship. The downloaded script is not provided, so its specific effects cannot be determined.
Piping an unpinned remote response directly into bash executes whatever the installer endpoint supplies with the invoking user's privileges; the PowerShell alternative has the same risk. Compromise of the distribution endpoint or installer could lead to local data theft or modification, although the file provides no evidence that the endpoint is currently malicious.
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 setup directs execution of downloaded shell or PowerShell code without explaining the local execution risk or requiring approval for software installation. The missing-CLI condition limits exposure, but permission to perform AfterShip operations does not necessarily authorize executing an installer on the user's machine.
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