Security audit
Security checks for vulnerabilities and agentic risk
The Perigon search workflow fits its purpose, but its automatic setup executes unverified downloaded code without a clear approval step.
Review setup before enabling this skill. Install a verified CLI version separately and require approval before running downloaded installers. Check the CLI's automatic skill synchronization and disable unwanted changes. Perigon queries and authorization use OOMOL and may incur charges. External installer and service implementations were not verified; no malicious behavior was established in the bundled file.
The supplied code performs remote installer execution rather than the declared Perigon data operations. Although installation can be a supporting implementation detail, this chunk establishes no relationship between the Oomol installer and the declared functionality. The downloaded script's contents and resulting system changes cannot be determined from the supplied code.
Piping a mutable remote installer directly into bash executes its contents without inspection, version pinning, or independent integrity verification. HTTPS protects transport but does not prevent a compromised distribution endpoint from serving code that can access local files, credentials, or other resources available to the process; the PowerShell example presents the same underlying 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 fallback setup instructs the agent to execute downloaded shell or PowerShell code without first obtaining explicit approval for installing software and modifying the host. Triggering setup only when the CLI is missing reduces exposure, but a compromised installer could still execute arbitrary code with the agent process's 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