Security audit
Security checks for vulnerabilities and agentic risk
The PartnerStack reads fit the stated purpose, but missing-tool setup directs the agent to execute unverified remote code without a clear user approval step.
Review the setup before enabling this skill. Install a reviewed, pinned oo release separately and approve any changes to other agent skills. PartnerStack access is routed through your OOMOL-connected account. The remote installers were unavailable for inspection, so their exact local effects remain unknown.
The supplied chunk contains no PartnerStack data-access behavior; its sole operation is executing a remotely fetched installer. Although CLI installation can be a supporting implementation detail, nothing supplied establishes this installer's connection to the declared PartnerStack functionality. The remote script's further actions cannot be determined from this chunk.
The command pipes an unpinned remote script directly into Bash without verifying its integrity or authenticity beyond HTTPS. If the distribution endpoint or release pipeline is compromised, attacker-controlled code would execute with the invoking user's privileges and could access local files and credentials; the PowerShell alternative has the same trust problem.
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 execute a remote installer without first explaining its system changes or obtaining installation-specific approval. This crosses from a read-only data request into local code execution; the missing-command condition limits when it happens but does not authorize that escalation.
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