Security audit
Security checks for vulnerabilities and agentic risk
The ORCID searches fit the stated purpose, but setup tells the agent to execute an unverified downloaded installer without a clear approval step.
Review the setup before installing. Prefer a separately verified CLI installation, and require approval before the agent downloads or executes installers. Confirm whether the CLI will install or update other agent skills. ORCID requests are routed through OOMOL using its connected account; the listed actions only read public data. The remote installer and hosted connector implementation were not available for verification.
The supplied command performs remote code execution for an apparent CLI installation, not ORCID searching or reading. Nothing in the supplied chunk establishes this installation as a supporting dependency for ORCID functionality. The downloaded script's contents and any subsequent effects are not available for assessment.
The command pipes a remotely fetched, unpinned script directly into Bash without checking its integrity or contents; the PowerShell example uses the same fetch-and-execute pattern. A compromised distribution endpoint or altered installer could execute arbitrary commands with the agent's local privileges, potentially exposing accessible files and credentials. The legitimate vendor domain and setup-only condition reduce suspicion of malicious intent but do not remove the supply-chain risk.
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 by executing downloaded code without first explaining the system changes or obtaining approval. Although conditional setup limits exposure, a request to read public ORCID data does not inherently authorize arbitrary local software installation, which can modify files and execute with the agent process's permissions.
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