Security audit
Security checks for vulnerabilities and agentic risk
The Crossref workflow is coherent, but setup can execute unverified downloaded code without clear user approval.
Review setup before installing. Use a reviewed, pinned CLI and require approval for installation changes. Check its automatic skill synchronization settings. Queries and references go through OOMOL and may incur charges. Installer contents and hosted connector behavior were not verified; no malicious behavior was established.
The supplied command does not query Crossref or read its data. It executes an external installer from cli.oomol.com, an undeclared capability with no demonstrated connection to the stated Crossref purpose. The mismatch is based on this visible behavior, not assumptions about what the remote script contains.
The supplied command performs login rather than the declared Crossref data operations. Nothing in the code establishes that this authentication is a supporting step for Crossref access.
Piping a downloaded installer directly into bash executes mutable remote content with the agent process's privileges, without an independent integrity check or review. Compromise of the distribution endpoint could therefore enable arbitrary code execution, credential theft, or local data modification; the Windows installer uses an equivalent download-and-execute pattern.
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
A missing CLI causes the instructions to escalate a read-only research task into software installation without requiring informed user approval. The conditional setup limits when this occurs, but does not authorize changes to the user's environment or explain that downloaded code will execute.
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