Security audit
Security checks for vulnerabilities and agentic risk
The Censys workflow is coherent, but its setup fallback runs unverified downloaded code without a clear user checkpoint.
Review and verify the CLI installation separately, and require approval before automatic setup changes your machine. Understand that OOMOL intermediates Censys requests and manages the connected API key. The external installer and CLI were not validated by this artifact review.
The supplied command performs no visible Censys search or data retrieval. Instead, it executes an Oomol-hosted installer, with no demonstrated role as a supporting dependency for the declared Censys functionality. The downloaded script is not supplied, so its additional behavior cannot be determined.
The entire supplied implementation is a login command, with no visible Censys search or read functionality and no established connection between oo and Censys. Authentication could be a supporting implementation detail in a larger Censys workflow, but no such workflow is present in this chunk. The authentication destination and any subsequent credential handling cannot be determined.
Piping an unpinned HTTPS download directly into bash executes whatever the endpoint returns without an integrity check or review. Although the domain matches the documented CLI provider and setup is conditional, compromise of the distribution path could lead to arbitrary code execution with access to local files and credentials; this overlaps with the setup-safety 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 fallback directs the agent to execute downloaded shell or PowerShell code without reviewing or verifying it or obtaining explicit approval for installation. A compromised installer source could execute arbitrary code with the agent's local permissions; the missing-CLI condition limits exposure but does not make automatic installation safe.
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