Security audit
Security checks for vulnerabilities and agentic risk
The Elasticsearch workflow has clear approval rules, but its automatic setup runs unverified remote code and may introduce broader agent changes.
Review and approve the CLI installation separately before enabling this skill, including any installation or synchronization of other agent skills. Use a verified release and narrowly scoped Elasticsearch credentials. OOMOL mediates database access, so consider whether that suits your data. Preserve the explicit approval requirements for writes and deletions, and avoid blindly retrying timed-out deletions: the artifact warns they may continue running. Remote installer behavior and hosted safeguards remain unverified; no malicious intent was established.
The supplied code performs remote installer execution rather than Elasticsearch operations. Nothing in the chunk establishes that the Oomol installer is a supporting dependency for the declared Elasticsearch functionality. The mismatch is based on the visible download-and-execute behavior, not assumptions about the remote script's contents.
The supplied chunk performs only an authentication command and shows no Elasticsearch operations or connection to Elasticsearch. Authentication could be a supporting implementation detail if that connection were established, but the supplied content does not establish it.
Piping a mutable remote installer directly into bash executes its contents with the invoking user's privileges without integrity verification or inspection. HTTPS protects transport but does not protect against a compromised publisher or distribution endpoint, potentially exposing local files and credentials; this overlaps with the setup-workflow finding.
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 setup fallback instructs the agent to execute downloaded shell or PowerShell scripts without verifying their contents or obtaining installation-specific approval. Installation is relevant to the skill, but it changes the local environment and could execute attacker-controlled code if the distribution channel is compromised; the missing-CLI condition reduces frequency, not impact.
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