Security audit
Security checks for vulnerabilities and agentic risk
The read operations fit the skill’s purpose, but its automatic setup can execute unverified remote code and introduce undisclosed changes to installed agent skills.
Review and approve the CLI installation separately before allowing automatic setup. Prefer a pinned, integrity-verified installation and decide whether bundled agent skills should be synced; the [CLI reference](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md) documents OO_SKILLS_SYNC_DISABLED. OOMOL mediates connected-account access. The exact remote installers remain unverified; the artifacts do not establish malicious intent.
The supplied chunk performs remote installer execution, not the declared Social Fetch data operations. Nothing in the supplied material establishes this installer as a necessary supporting dependency. The downloaded script is not included, so its specific effects and permissions cannot be determined.
Authentication can be a supporting implementation detail, but the supplied chunk contains only a login command and establishes no connection to Social Fetch or its declared data-access functions. Its visible primary behavior therefore differs from the declared purpose.
The command pipes a mutable network response directly into Bash without pinning or verifying its contents; the PowerShell alternative uses the same download-and-execute pattern. Compromise of the installer endpoint or its distribution infrastructure could execute attacker-controlled code with the invoking user's privileges, exposing local files and credentials even though Social Fetch tokens are handled server-side.
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
A missing CLI triggers instructions to install software using remotely supplied code without first explaining the system changes or requesting approval. This extends a read-oriented task into local software installation; the missing-command condition limits exposure but does not establish user consent.
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