Security audit
Security checks for vulnerabilities and agentic risk
This Writer helper needs review because its setup automatically executes an unverified installer and its CLI can change agent skills beyond this integration.
Review and approve CLI installation separately, using a verified release instead of automatically executing the download. Check the CLI's automatic skill synchronization before use, and understand that Writer prompts pass through OOMOL. The remote installers and hosted connector implementation were unavailable for inspection; no malicious behavior was established.
The supplied command performs no visible Writer search or read operation. Instead, it executes an external installer from an Oomol domain. The provided code does not establish this installation as a supporting implementation detail for Writer access. The downloaded script is not supplied, so its specific effects cannot be determined.
Piping an HTTPS response directly into bash executes mutable remote code without inspecting it or verifying a pinned artifact. Compromise of the distribution endpoint or installer supply chain could execute attacker-controlled commands with the invoking user's permissions, potentially exposing local files and credentials; the PowerShell example has the same underlying risk.
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 missing-command fallback directs installation without requiring user approval or explaining that downloaded code will execute and may modify the local system. Restricting this fallback to a missing CLI reduces exposure, but a request to access Writer does not necessarily authorize software installation; the approval rules for Writer writes do not cover this local change.
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