Security audit
Security checks for vulnerabilities and agentic risk
The Shorten.REST workflow is coherent, but setup can execute unchecked downloads and the required CLI can change other agents’ installed skills without clear disclosure.
Review and install a fixed CLI release yourself before use. The publisher documents OO_SKILLS_SYNC_DISABLED=1 to prevent startup synchronization into other agents’ skill directories. Confirm that OOMOL may process your Shorten.REST requests and retain the skill’s approval requirements for changes and deletions. The remote installer contents and exact installed release could not be verified.
The supplied command installs software from an Oomol endpoint rather than performing any visible Shorten.REST operation. Nothing in the provided code establishes that this installation is a supporting requirement for the declared purpose. The remote script's contents are unavailable, so its further behavior cannot be determined.
Authentication could be a supporting implementation detail, but the supplied chunk consists entirely of a login command, with no Shorten.REST reference or data-operation workflow establishing that connection. Its demonstrated purpose therefore differs materially from the declared purpose.
Piping the HTTPS response directly into bash executes mutable remote content without first verifying its integrity or reviewing it. The endpoint is relevant to the required CLI, but a compromised distribution source could still run arbitrary commands with the user's privileges; this is the same underlying installation risk flagged by SQP-2.
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 execution of remotely downloaded shell or PowerShell code without an explicit installation approval step or integrity verification. If the installer source is compromised, code could execute with the invoking user's privileges; limiting installation to a missing-CLI error reduces exposure but does not remove the risk.
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