Security audit
Security checks for vulnerabilities and agentic risk
The calendar-reading workflow fits its purpose, but missing-tool setup directs the agent to run an online installer without confirming its scope or getting separate approval.
Review and approve the CLI installation separately before allowing this fallback setup. Prefer a pinned, verified release and check whether it installs other agent skills. Connecting NeetoCal entrusts OOMOL with account access and calendar requests. The exact installer payload was unavailable for verification; this Review verdict concerns installation controls, not evidence of malicious intent.
The supplied code executes an external installer rather than searching or reading NeetoCal data. Nothing in the chunk establishes this installation as a supporting dependency for NeetoCal access. The downloaded script's contents and downstream effects are not provided, so those effects cannot be determined.
The command pipes a remotely fetched, unpinned script directly into Bash without an independent integrity check or review opportunity; the PowerShell example has the same underlying risk. If the distribution endpoint or release infrastructure is compromised, attacker-controlled code executes with the agent process's local permissions, potentially exposing accessible credentials or modifying files. The legitimate provider relationship and HTTPS do not eliminate this supply-chain 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
When the CLI is missing, the workflow directs the agent to install software without requiring user approval or describing the installer's local effects. This expands a read-only NeetoCal request into local code execution and potentially persistent environment changes; the missing-command condition reduces exposure but does not establish authorization.
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