Security audit
Security checks for vulnerabilities and agentic risk
The Skio read operations fit the stated purpose, but missing software triggers remote installation without clear user approval.
Review the CLI installation before enabling automatic setup. Use a verified, fixed release and explicitly approve local changes. Check its cross-agent skill synchronization settings and limit Skio permissions to the reads you need. The remote installer contents remain unverified; no malicious behavior was established.
The supplied command performs remote script execution rather than searching or reading Skio data. Although installation can be a supporting implementation detail, this chunk establishes no relationship between the Oomol installer and the declared Skio functionality. The downloaded script is not supplied, so its specific actions cannot be determined.
The command pipes a remotely fetched, unpinned script directly into Bash, allowing the delivered content to execute with the agent's local permissions without prior verification. The PowerShell alternative has the same weakness; compromise of the distribution endpoint could turn legitimate dependency setup into arbitrary code execution, although the file provides no evidence of an actual compromise.
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 instructs the agent to install software when the CLI is missing, without first explaining local changes or obtaining explicit installation approval. A request to read Skio data does not inherently authorize executing an installer with the agent's local permissions; the missing-command condition limits exposure but does not establish that authorization.
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