Security audit
Security checks for vulnerabilities and agentic risk
The Stay AI reading workflow fits its purpose, but automatic setup executes unchecked remote code and leaves broader local changes unclear.
Review setup before installing: use a verified CLI release and approve its local changes, including any automatic installation of other agent skills. Connect only the needed Stay AI account and permissions, understanding that requests pass through OOMOL. The remote installer and server-side credential handling remain unverified; no malicious behavior was established.
The supplied code performs a remote installer execution rather than searching or reading Stay AI data. No connection between the Oomol installer and the declared functionality is established in the supplied content, so this cannot be treated as a demonstrated supporting implementation detail. The downloaded script's further actions are not visible.
The command pipes a remotely fetched, unpinned script directly into Bash without an independent integrity check; the PowerShell alternative uses the same download-and-execute pattern. If the distribution endpoint or release pipeline is compromised, attacker-controlled code could execute with the agent's local privileges, exposing accessible files and credentials despite Stay AI credentials being injected server-side.
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 skill directs the agent to execute a remote installer without requiring approval for arbitrary code execution or local software changes. Limiting this behavior to first-time setup reduces exposure, but a request to read Stay AI data does not itself authorize installing software with the agent's local privileges.
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