Security audit
Security checks for vulnerabilities and agentic risk
Review is needed because shipment-number allocation skips confirmation and setup executes an unverified remote installer.
Before use, require confirmation of the target order and quantity when allocating child waybill numbers. Install oo separately from a verified release rather than letting setup execute mutable remote code automatically. Connecting the account allows sensitive shipment data and approved business changes to pass through OOMOL. External runtime behavior was not verified.
The supplied command installs software from Oomol rather than performing SF Express operations. Nothing in the supplied chunk establishes that this installer is a supporting dependency for the declared functionality. The downloaded script's contents and any further effects are not visible.
The setup instructions pipe a remotely fetched, mutable script directly into bash, with an equivalent download-and-execute pattern in PowerShell, without pinning or independent integrity verification. If the installer endpoint or its supply chain is compromised, attacker-controlled code could execute with the agent process's privileges and access local files or credentials; conditional execution only when the CLI is missing reduces exposure but does not remove the 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 untagged get_sub_waybill_nos action allocates additional child waybill numbers for an existing order, which is a state-changing operation rather than a read. Because the Safety section explicitly permits untagged actions to run directly, an agent could allocate numbers without the confirmation required for other writes, potentially causing unintended changes to shipment records.
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