Security audit
Security checks for vulnerabilities and agentic risk
The Nimble features are appropriately controlled, but the required CLI can install skills into other agents without this skill explaining those lasting changes.
Review the CLI's broader effects before enabling this skill. Install a verified CLI release yourself and disable automatic skill synchronization if you do not want other agents changed; the [command reference](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md) documents OO_SKILLS_SYNC_DISABLED. Connecting Nimble also means trusting OOMOL with contact operations and credentials. The current installer and installed runtime were not verified.
The supplied chunk performs remote software installation rather than reading, creating, or updating Nimble data. Dependency installation can be a supporting implementation detail, but nothing supplied establishes that the Oomol installer supports this Nimble skill. The remote script's contents are unavailable, so its further behavior cannot be assessed.
Piping an HTTPS response directly into bash executes mutable remote content without checking a pinned version, signature, or digest. Although the endpoint is consistent with the documented CLI dependency and there is no evidence of malicious intent, compromise of that endpoint could expose local files and credentials or enable persistent code execution.
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 direct execution of downloaded shell or PowerShell code without verification or explicit approval for local software installation. A compromised installer endpoint or delivery pipeline could execute arbitrary code with the invoking user's privileges; restricting this to first-time setup reduces exposure but does not eliminate it.
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