Security audit
Security checks for vulnerabilities and agentic risk
The note-management controls are clear, but setup directs the agent to execute unverified downloaded code without explicit installation approval.
Review the CLI installation separately before enabling setup, and require approval before executing downloaded installers. Check its automatic bundled-skill installation behavior. Connecting your account permits access to private notes through OOMOL; retain the skill's explicit approval requirements for changes and deletions. The installer and remote connector implementation were not verified.
The supplied code performs remote installer execution, not Fast Note Sync operations. Although dependency installation can be a supporting implementation detail, nothing in this chunk establishes that the Oomol installer supports the declared service. The downloaded script's contents and any further effects are not visible.
Piping a remotely fetched script directly into bash executes mutable third-party code with the invoking user's permissions, without inspecting or independently verifying it. A compromised distribution endpoint could therefore execute arbitrary commands or access local secrets; the PowerShell alternative has the same underlying risk, although there is no evidence here that either endpoint is malicious.
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-CLI fallback directs the agent to execute third-party installer code without requiring informed approval for local software installation. Restricting installation to a missing-dependency error reduces exposure, but consent to manage notes does not necessarily authorize executing an installer or modifying the local environment.
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