Fomo

• Outcome: Review
• Latest audit: Nov 3, 2026 · 11:46 AM UTC
• Version: 1.0.5

Overview

Fomo changes require your approval, but the setup instructions execute unchecked downloads and omit broader changes the CLI can make to installed agent skills.

Review and install a verified CLI release yourself before enabling this skill. Check its automatic skill-installation behavior; the publisher documents OO_SKILLS_SYNC_DISABLED=1 to disable startup synchronization. Keep the Fomo write and deletion confirmations, and connect only the account you intend to use. The remote installers were unavailable for inspection, and the skill does not pin the CLI implementation. No malicious intent or exfiltration was established.

A.I.G

Vulnerability Patterns

• Skill Instruction Hijacking: Alters the agent's session goals or safety constraints when the skill loads
• Agent Memory Poisoning: Writes attacker-controlled rules into memory that affect later sessions
• Remote Payload Retrieval and Execution: Fetches external code whose behavior can change after review
• Embedded Malicious Code: Ships malicious scripts inside the skill and executes them locally
• Unauthorized Access and Privilege Escalation: Obtains permissions beyond the task's legitimate needs

SkillSpector

Vulnerability Patterns

• Supply Chain: Unpinned Dependencies, External Script Fetching, Obfuscated Code
• Excessive Agency: Unrestricted Tool Access, Autonomous Decision Making, Scope Creep
• MCP Tool Poisoning: Hidden Instructions, Unicode Deception, Parameter Description Injection
• Prompt Injection: Instruction Override, Hidden Instructions, Exfiltration Commands
• Data Exfiltration: External Transmission, Env Variable Harvesting, File System Enumeration

Findings (3)

Description-Behavior Mismatch

High

• Category: MCP Tool Poisoning
• Confidence: 94% confidence

Finding

The supplied chunk performs remote installer execution, not Fomo operations. Although installing a dependency can be a supporting implementation detail, nothing supplied establishes that this Oomol installer supports the declared Fomo functionality. The downloaded script's contents and any further effects are not available for assessment.

Content

No source excerpt is available for this finding.

External Script Fetching

High

• Category: Supply Chain
• Confidence: 98% confidence

Finding

The installation command immediately executes remotely fetched shell code without a pinned version or independent integrity verification; the PowerShell alternative has the same weakness. A compromised distribution endpoint or modified installer could execute arbitrary code with the agent process's permissions, exposing local credentials and files. Conditional setup reduces exposure, and an independently enforced Bash(oo *) allowlist could block installation, but neither makes this installation instruction intrinsically safe.

Content

Scanner excerpt · SKILL.md (reported line 59)May include surrounding context.

• oo: command not found — install the oo CLI (other platforms: https://cli.oomol.com/install-guide.md):

  bash

  curl -fsSL https://cli.oomol.com/install.sh | bash    # macOS / Linux
  

  powershell

Autonomous Decision Making

Medium

• Category: Excessive Agency
• Confidence: 80% confidence

Finding

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.

Content

Scanner excerpt · SKILL.md (reported line 80)May include surrounding context.

md

- **`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