Security audit
Security checks for vulnerabilities and agentic risk
Stannp changes require approval, but the fallback setup runs unverified remote code without a separate approval step.
Review and approve CLI installation separately, using a verified release, and review its bundled-skill synchronization settings. OOMOL mediates access to your connected Stannp account. Keep the skill's confirmation requirements for changes and deletions. The remote installer contents and exact system effects remain unverified; no malicious intent was established.
The supplied code is a remote installer invocation rather than a Stannp integration. Installing dependencies can be a supporting implementation detail, but nothing in this chunk establishes that this installer supports Stannp requests. The downloaded script's contents are not supplied, so its further behavior cannot be determined.
Piping an HTTPS response directly into bash executes mutable remote content without checking a pinned version, signature, or independently trusted digest. Although this is a relevant CLI setup step rather than evidence of malicious intent, compromise of the distribution endpoint could expose local files and credentials or modify the host.
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 remotely downloaded shell or PowerShell code without an explicit installation approval or integrity-verification step. Restricting this to a missing-CLI error reduces exposure, but a compromised installer could still execute arbitrary code with the invoking user's permissions; the declared tool restriction may limit execution but should not be relied on as the sole safeguard.
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