Security audit
Security checks for vulnerabilities and agentic risk
The Lessonspace workflow is coherent, but its setup can automatically execute unverified remote installation code without separate user approval.
Review the setup before installing. Prefer an independently verified, pinned CLI release, approve local installation separately, and review or disable automatic bundled-skill changes. OOMOL will mediate Lessonspace access; handle recording links and room credentials carefully. The remote installers and backend credential handling were not verified.
The supplied code executes an Oomol-hosted installer and contains no visible Lessonspace operations or evidence connecting that installer to Lessonspace functionality. Although dependency installation can be a supporting implementation detail, no such relationship is established here. The remote script's contents and any subsequent behavior are not available for assessment.
The command executes a mutable remote script with the agent process's permissions without pinning a version or verifying integrity or authenticity beyond HTTPS. A compromised distribution endpoint could therefore execute arbitrary code and access locally available data or credentials; the legitimate dependency context and missing-CLI condition reduce exposure but 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 directs the agent to install software after a missing-command error without requiring user approval or explaining that downloaded code will execute and may change the local system. Its conditional nature reduces exposure, but approval requirements for Lessonspace writes do not cover this local installation side effect.
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