Security audit
Security checks for vulnerabilities and agentic risk
Review before installing: setup can execute unverified remote code and introduce additional agent skills without clearly requesting approval.
Review and approve CLI installation separately, using a verified release. Consider setting OO_SKILLS_SYNC_DISABLED=1 before invoking the CLI to prevent the documented startup skill synchronization. Connect only the intended Simplesat account and review customer updates and survey emails before execution. The artifacts support setup and disclosure concerns, but do not establish malicious intent or data theft.
The supplied command performs remote installer execution, with no visible Simplesat API operations or demonstrated relationship to the declared Simplesat functionality. Nothing in the supplied chunk establishes this installation as a supporting dependency. The downloaded script's further behavior cannot be determined from the provided code.
Piping a mutable remote installer directly into bash executes its contents without prior inspection, version pinning, or independent integrity verification. HTTPS protects transport but not against compromise of the distribution service, so this fallback introduces a supply-chain path to code execution with the agent's privileges; the PowerShell alternative has the same weakness.
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
When the CLI is missing, the fallback directs the agent to execute downloaded shell or PowerShell code without explicitly obtaining approval for local software installation. A Simplesat data request does not necessarily authorize arbitrary local code execution, and a compromised installer could access files and credentials with the agent's privileges; the conditional setup limits exposure but does not remove it.
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