Security audit
Security checks for vulnerabilities and agentic risk
The AppleDB lookup workflow is coherent, but a missing command can trigger execution of an unverified remote installer without a user approval step.
Review and approve CLI installation separately before allowing this skill to perform lookups, preferably using a verified release. Requests go through OOMOL and may require its account or credits. The review concern is the automatic remote-install fallback; the artifact does not establish malicious behavior, and the external installer and CLI were not audited.
The supplied command performs remote installer execution, not AppleDB data access. Nothing in the chunk establishes that this installation is a supporting requirement for AppleDB. The installer contents are not provided, so its downstream actions cannot be determined.
The supplied command performs authentication rather than searching or reading AppleDB data. Authentication could be a supporting implementation detail if tied to the declared service, but this chunk provides no evidence of such a connection.
Piping a mutable HTTPS response directly into Bash executes whatever code the installation endpoint supplies, without a pinned artifact or independent integrity verification. A compromised distribution endpoint could therefore execute arbitrary commands with the invoking user's permissions; the PowerShell alternative 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 fallback instructs the agent to execute downloaded installation scripts without explicitly obtaining approval for executing remote code or changing the local system. Restricting this to a missing-CLI error reduces exposure, but a read-only AppleDB request can still trigger a materially more privileged setup workflow.
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