Security audit
Security checks for vulnerabilities and agentic risk
Task operations have clear approval safeguards, but setup can execute changing third-party code and install additional agent skills without separate approval.
Review the setup path before installing. Use a separately reviewed, verified CLI release and decide whether to allow its automatic agent-skill synchronization. Understand that OOMOL mediates access to your task data. Keep the skill's existing confirmation requirements for changes and deletion. The remote installers and hosted implementation were not verified.
The supplied chunk executes a remote installation script rather than interacting with Microsoft To Do. Dependency installation can be a supporting implementation detail, but no connection between this installer and the declared functionality is established here. The downloaded script's contents and further effects are not available for assessment.
Piping a live HTTPS response directly into bash executes remote code without inspecting it or verifying a pinned release or signature; the PowerShell alternative has the same issue. Compromise of the distribution endpoint or installer supply chain could result in arbitrary code execution with the invoking user's privileges, although the missing-CLI prerequisite limits when this path is reached.
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 setup instructions direct the agent to execute downloaded scripts when the CLI is missing without explicitly obtaining approval for third-party code execution and local system changes. Although this is a legitimate dependency setup path, consent to manage cloud tasks does not necessarily authorize installing software on the local machine.
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