Security audit
Security checks for vulnerabilities and agentic risk
The Moxie reading features fit their purpose, but automatic setup runs an unverified remote installer without a separate approval step.
Require approval before setup and review a pinned CLI release before installing it. Check whether its installation of additional agent skills is acceptable, and connect only the intended Moxie account through OOMOL. The Review verdict concerns automatic setup and persistent effects; the artifact does not establish malicious intent. Remote installer and hosted connector implementations remain unverified.
The supplied command executes an Oomol-hosted installer rather than searching or reading Moxie data. Nothing in the supplied chunk establishes this installation as a supporting dependency for the declared purpose. The downloaded script's contents are not provided, so its further effects cannot be determined.
The command downloads a mutable remote script and immediately executes it with the agent process's privileges, without integrity verification or review; the PowerShell alternative has the same weakness. Compromise of the distribution endpoint could therefore lead to local code execution and access to files or credentials available to that process, although the missing-CLI condition 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 fallback instructs the agent to install software after a missing-command error without first obtaining approval for local system changes. A request to read Moxie data does not inherently authorize installing executable software; the conditional trigger reduces exposure but does not establish consent.
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