Security audit
Security checks for vulnerabilities and agentic risk
The APIVoid functions fit the description, but the required CLI can silently install lasting instructions into other agents without this skill explaining that effect.
Review the CLI setup before enabling this skill. Use a reviewed, fixed CLI release and decide whether you want its additional agent skills. Supporting versions provide OO_SKILLS_SYNC_DISABLED=1 to prevent startup skill synchronization; configure it before invoking the CLI. Submit only lookup data you intend to share with OOMOL and APIVoid, removing URL credentials or tokens. The external installers and server-side connector were not verified by this artifact review.
The supplied command executes an external installer and contains no APIVoid interaction. Nothing in the supplied material establishes that this installer is a supporting dependency for APIVoid access. Its resource access and installation behavior therefore materially differ from the declared purpose. The downloaded script's contents and further effects are not available for assessment.
The supplied code only invokes a CLI login command; it does not search or read APIVoid data. Authentication could support an APIVoid integration, but nothing in this chunk establishes that connection, so the observed behavior materially differs from the declared purpose.
Piping a mutable HTTPS response directly into Bash executes whatever the installation endpoint supplies without review, version pinning, or artifact verification. Compromise of the provider's distribution infrastructure could therefore execute attacker-controlled code with the user's permissions; HTTPS does not protect against a compromised publisher. This is the same underlying installation risk identified in the setup-warning finding, not a separate exploit chain.
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
Calling every read action safe conflates absence of state changes with absence of disclosure risk. Reputation and email lookups transmit their inputs through OOMOL to APIVoid, potentially exposing private addresses, internal hostnames, or secrets embedded in URLs; an explicit user request to check a public indicator reduces this concern but does not justify blanket permission for all lookup inputs.
The missing-CLI fallback directs execution of downloaded shell or PowerShell code without a separate approval step or integrity verification. This can modify the host and execute with the invoking user's permissions; its conditional, documented setup role reduces exposure but does not remove the supply-chain risk.
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