Security audit
Security checks for vulnerabilities and agentic risk
The log-reading workflow is coherent, but missing-tool recovery tells the agent to execute unverified downloaded installers without a clear user approval step.
Review the setup behavior before enabling this skill. Prefer installing a reviewed, fixed CLI version yourself and requiring approval for further installation changes. Check its automatic skill synchronization and grant only necessary SLS read access. The remote installers and hosted connector remain unverified; the scanner's partial-reference gaps were resolved by reading the complete bundled file.
The supplied command performs remote script execution rather than an SLS search or read operation. Although installing a relevant client could be a supporting implementation detail, the supplied chunk does not establish that this installer supports the declared SLS functionality. The downloaded script's contents and any further effects cannot be determined from this snippet.
The command pipes a mutable HTTPS response directly into bash without verifying the script's integrity or provenance beyond its hosting endpoint. Compromise of that endpoint or its delivery infrastructure could turn dependency installation into arbitrary local code execution; HTTPS protects transport but does not establish that the downloaded code is safe.
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 missing-CLI recovery path directs the agent to execute remote shell or PowerShell code without an explicit approval gate, integrity verification, or disclosure of local system changes. A compromised installer could execute with the agent's local permissions, potentially accessing files and credentials; the missing-CLI condition limits exposure but does not make installation equivalent to a read-only SLS operation.
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