Security audit
Security checks for vulnerabilities and agentic risk
Linear changes require approval, but setup executes unverified downloaded code and does not disclose the CLI’s broader agent-skill installation behavior.
Review and approve CLI installation separately before allowing the setup fallback. Consider disabling its automatic skill synchronization; current documentation provides OO_SKILLS_SYNC_DISABLED=1 for this purpose. Only connect Linear data you authorize OOMOL to handle, and retain the skill’s approval requirements for changes. The remote installers and binaries were not verified. [CLI controls](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md)
The supplied command installs external software rather than performing any visible Linear operation. Nothing in the chunk establishes that this installer is a supporting dependency for the declared Linear functionality. The downloaded script is not provided, so its further behavior and any relationship to Linear cannot be verified.
Piping a mutable HTTPS installer directly into Bash executes remotely supplied code without an opportunity to verify or review it. HTTPS protects transport but does not protect against a compromised publisher or installer host, which could use this execution path to access local files and credentials within the process's permissions; this overlaps with SQP-2 rather than representing a separate attack chain.
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 execute a downloaded installer through Bash or PowerShell without requiring explicit installation approval or verifying the downloaded artifact. A compromised installer endpoint or publisher could execute arbitrary code with the agent's local permissions; limiting setup to a missing-CLI error reduces frequency but does not eliminate this risk.
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