Security audit
Security checks for vulnerabilities and agentic risk
This PubMed skill needs review because its setup directs the agent to run unverified downloaded software without a separate approval step.
Verify and install the OOMOL CLI yourself before enabling this skill, and prevent automatic execution of its installer fallback. Review the CLI's installation of additional agent skills and understand that PubMed requests pass through OOMOL and may use credits. The PubMed workflow shows no malicious intent, but the remote installer and its full effects remain unverified.
The supplied command performs a login operation and contains no PubMed search or reading functionality. Nothing in the supplied code connects this authentication step to PubMed, so it is not established as a supporting implementation detail of the declared purpose.
The supplied command does not access PubMed or implement PubMed search or reading. It executes an external installation script from cli.oomol.com, with no demonstrated connection to the declared PubMed functionality. The remote script's contents and further effects cannot be determined from this chunk.
Piping a mutable HTTPS response directly into bash executes whatever the installer endpoint supplies, without pinning or verifying the artifact. Compromise of the distribution endpoint could therefore compromise the local agent environment; HTTPS protects transport but does not establish that the delivered script is trustworthy.
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 an explicit approval step or integrity verification. Although it runs only when the CLI is missing, a compromised installer source could execute arbitrary code with the agent process's privileges; this is unnecessary exposure for a read-only PubMed task.
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