Security audit
Security checks for vulnerabilities and agentic risk
The Qichacha lookup workflow fits its purpose, but its fallback setup executes downloaded software without verification or a clear approval step.
Review and approve CLI installation separately before allowing this skill to perform setup. Prefer a pinned, verified installation. Expect queries and connected-account access through OOMOL, with possible service charges. The bundled instructions were fully inspected, but external installer and connector behavior remain unverified.
The supplied command invokes an Oomol installer rather than searching or reading Qichacha data. Nothing in the chunk establishes that this installation supports the declared Qichacha functionality. The downloaded script's contents are not supplied, so its exact effects cannot be determined.
The curl-to-bash command immediately executes mutable remote content without verifying a pinned artifact or inspecting the script. HTTPS protects transport but does not prevent a compromised distribution endpoint from supplying code that can access local files and credentials with the executing user's permissions; this is the same underlying installer risk identified by SQP-2.
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 setup instructs the agent to execute remotely supplied shell or PowerShell code without prior review, integrity verification, or explicit user approval for installation. Although triggered only when the CLI is missing, this can turn a data-retrieval request into local code execution with the agent's privileges if the installer distribution is compromised; the missing warning alone is not the underlying vulnerability.
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