Security audit
Security checks for vulnerabilities and agentic risk
The LogSnag workflow requires approval for data changes, but setup directs the agent to execute a remote installer without a separate approval step.
Review and install the CLI separately before enabling this skill, including any automatic agent-skill synchronization. Understand that LogSnag requests and connected credentials are handled through OOMOL. Keep the required confirmation before data changes. The remote installer was unavailable for inspection; the review concern is setup authority and under-disclosed local effects, with no demonstrated malicious behavior.
The supplied command executes an Oomol-hosted installer, with no visible LogSnag integration or demonstrated dependency relationship. Although installation can be a supporting implementation detail, nothing supplied establishes that connection here. The remote script's contents and any further effects cannot be determined from this chunk.
The command pipes a mutable remote script directly into Bash without verifying a pinned artifact, signature, or independently trusted checksum; the PowerShell alternative has the same issue. A compromised distribution endpoint could execute arbitrary code with the invoking user's permissions, potentially accessing local credentials or modifying files. HTTPS and the legitimate prerequisite context reduce some concerns but do not protect against compromise of the script source.
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 without first obtaining explicit approval for local system changes or explaining that downloaded code will execute with the invoking user's permissions. Restricting installation to a missing-CLI error reduces exposure, but a request to operate LogSnag does not itself authorize installing software.
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