Security audit
Security checks for vulnerabilities and agentic risk
The LoyJoy workflow is coherent, but its setup can execute changing remote code and introduce broader agent changes without clear user approval.
Review and approve CLI installation separately, including any additional agent skills it installs or updates. Prefer a verified, fixed release and connect only the LoyJoy access you need. Keep confirmation enabled for writes. The bundled instructions were fully inspected, but the remote installer contents remain unverified.
The supplied command executes an Oomol-hosted installer and contains no LoyJoy interaction. Nothing in the supplied content establishes that installing this software supports the declared LoyJoy functionality, so this is a material mismatch rather than a demonstrated supporting implementation detail. The remote script's contents and any further effects are not available for assessment.
The command streams a mutable remote script directly into Bash without pinning a version or independently verifying its integrity; the PowerShell alternative has the same execution pattern. If the distribution infrastructure is compromised, following this setup instruction can execute attacker-controlled code with the agent's local privileges, potentially exposing files and credentials; HTTPS and a relevant vendor domain 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
The fallback instructs the agent to install software after a missing-command error without first explaining local changes or obtaining explicit installation approval. A user requesting LoyJoy data operations has not necessarily authorized executing downloaded code or modifying their environment; the conditional trigger limits 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