Security audit
Security checks for vulnerabilities and agentic risk
Faktoora changes require confirmation, but setup directs the agent to run unverified downloaded code without separate installation approval.
Review the CLI installation before allowing setup, and prefer an independently verified, fixed release. OOMOL will mediate access to your connected Faktoora account. Review its automatic agent-skill synchronization; the publisher documents OO_SKILLS_SYNC_DISABLED as a control. Keep the skill's confirmation requirements for project changes and deletion. This review found no artifact-backed malicious intent, but could not verify the downloaded installer.
The supplied command installs software from cli.oomol.com rather than performing or implementing identifiable Faktoora operations. Although installing a CLI could be a supporting implementation detail, the supplied chunk provides no evidence that this installer supports Faktoora. The downloaded script's further behavior cannot be determined from this code alone.
Piping a remote response directly into bash executes mutable network-delivered code with the agent process's local permissions, without a pinned version or independent integrity verification. A compromised distribution endpoint could therefore compromise accessible local files and credentials; HTTPS and the legitimate dependency relationship do not eliminate this supply-chain risk. The PowerShell example has the same underlying issue.
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 install software by executing downloaded scripts without explicitly requesting approval for local code execution or system changes. Limiting installation to a missing CLI reduces exposure, but the skill's confirmation rules cover Faktoora mutations rather than installation on the user's machine.
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