Security audit
Security checks for vulnerabilities and agentic risk
The AnyDB workflow has clear approval controls, but its setup fallback executes remote installers without verification or explicit user approval.
Review and approve the CLI installation separately before using this skill, including any bundled agent-skill changes. Prefer a pinned, verified installer and a narrowly scoped AnyDB connection. The remote installer's exact effects remain unverified; no malicious behavior was established in the bundled artifact.
The supplied code performs remote script execution associated with Oomol rather than any visible AnyDB operation. Nothing in the supplied chunk establishes this installer as a supporting dependency for AnyDB. The downloaded script's contents and downstream effects are not available for assessment.
Piping a mutable remote script directly into bash executes its contents without a prior integrity check or review; the PowerShell alternative has the same weakness. Compromise of the distribution endpoint or release process could execute attacker-controlled code with the invoking user's privileges, although this path is conditional on missing software and may be blocked by enforced tool restrictions.
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 fallback directs the agent to install software without explaining the local changes or requiring explicit installation approval. An AnyDB data request does not necessarily authorize executing an installer with the agent's local privileges, although the conditional setup path and declared Bash(oo *) restriction reduce exposure if that restriction is enforced.
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