Security audit
Security checks for vulnerabilities and agentic risk
Felt operations have clear approval controls, but setup can execute unverified remote code and introduce broader agent changes without separate user approval.
Review and approve CLI installation separately before enabling this skill. OOMOL will mediate Felt access, and its CLI may also install other agent skills. The publisher documents OO_SKILLS_SYNC_DISABLED=1 to disable startup skill synchronization in its [command reference](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md). The remote installers and hosted implementation remain unverified. Keep the skill's approval requirements for Felt writes and deletions.
The supplied code performs remote software installation rather than any demonstrated Felt operation. Although dependency installation can be a supporting implementation detail, the supplied content establishes no relationship between this Oomol installer and the declared Felt functionality. The downloaded script's further behavior is not visible and cannot be assessed.
The command executes a mutable remote script directly in Bash without a pinned version or independent integrity verification; the PowerShell alternative has the same underlying risk. Compromise of the distribution endpoint or release pipeline could execute attacker-controlled code with the invoking user's permissions, exposing local files and credentials despite server-side handling of Felt tokens.
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 skill directs installation without requiring informed approval for executing remote code or changing the local environment. The Felt write/destructive confirmation rules do not cover local software installation, so a routine Felt request could unexpectedly trigger broader system changes.
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