Security audit
Security checks for vulnerabilities and agentic risk
The PromptLayer reading workflow is coherent, but setup directs the agent to execute unverified downloaded software without a clear user approval step.
Review and approve CLI installation separately, inspect and verify the installer, and check its automatic agent-skill installation behavior. Connect only the intended PromptLayer account and consider whether its prompts and logs may be accessed through OOMOL. The Review verdict concerns insufficiently controlled setup; the artifacts do not establish malicious intent.
The supplied command performs remote script execution, not PromptLayer searching or reading. Nothing in the supplied chunk establishes the Oomol installer as a supporting dependency for PromptLayer, so this is a material mismatch rather than a demonstrated implementation detail. The downloaded script's further behavior cannot be determined from this chunk.
The command pipes a mutable remote script directly into Bash without verifying its contents, version, or integrity; the PowerShell alternative has the same execution pattern. If the distribution endpoint or installer supply chain is compromised, attacker-controlled code could execute with the agent process's privileges and access local data or credentials. HTTPS and the legitimate dependency context reduce some risks but do not provide artifact verification.
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
When the CLI is missing, the workflow directs the agent to install software without explicitly obtaining approval for local code execution and system changes. Although conditional setup is legitimate, a request to read PromptLayer data does not necessarily authorize installing software with the agent's local privileges.
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