Security audit
Security checks for vulnerabilities and agentic risk
The WaiverFile read functions fit their purpose, but setup can execute unverified downloaded code and introduce broader changes to installed agent skills without clear user control.
Review and approve CLI installation separately before using the skill. Confirm that OOMOL may process your waiver requests and manage the connected credentials. Review the CLI's automatic skill synchronization and disable it if unwanted. The external installer and runtime implementation are not bundled, so their exact behavior remains outside this artifact review; no malicious behavior was established.
The supplied code runs an Oomol-hosted installation script rather than performing a WaiverFile operation. Nothing in the provided chunk establishes this installation as a supporting dependency for WaiverFile access. The downloaded script is not supplied, so its specific effects cannot be determined.
Piping a mutable remote installer directly into Bash executes its contents without prior verification; the PowerShell alternative has the same issue. HTTPS protects transport but does not prevent a compromised publisher or distribution endpoint from serving code that accesses local files, credentials, or other resources available to the user.
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 installation code without explaining the local code-execution implications or requiring explicit approval for installation. Although conditional on a missing CLI, this can turn a read-only WaiverFile request into arbitrary code execution with the invoking user's permissions if the installer source is compromised.
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
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
## Resources
- WaiverFile homepage: https://www.waiverfile.com
- API documentation: https://api.waiverfile.com/swagger/ui/index