Security audit
Security checks for vulnerabilities and agentic risk
This Daffy reader needs review because its setup directs the agent to execute unverified downloaded code without a clear user checkpoint.
Install a reviewed, pinned CLI separately before using this skill. Review OOMOL's access to Daffy financial information and its automatic agent-skill synchronization; the [command reference](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md) documents OO_SKILLS_SYNC_DISABLED. The remote installer and hosted connector implementations remain unverified.
The supplied chunk performs an external installation step rather than any visible Daffy data operation. No evidence establishes this installer as a necessary supporting implementation detail for Daffy access. The downloaded script's contents are not supplied, so its further actions cannot be determined.
The supplied code only initiates login; it contains no Daffy search or read operation and establishes no connection between oo and Daffy. Authentication could be a supporting implementation detail if that connection were shown, but the supplied chunk instead presents authentication as its sole behavior.
Piping an unpinned HTTPS response directly into Bash executes whatever code the installer endpoint supplies, without an integrity check or review opportunity. A compromised distribution endpoint could therefore execute arbitrary commands with the agent process's local privileges; the PowerShell alternative has 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 missing-CLI fallback directs the agent to execute remotely supplied installation code without explicitly obtaining approval for local system changes. Although installation is relevant to the connector and conditional on a missing dependency, it crosses from reading Daffy data into executing code with the local user'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