Security audit
Security checks for vulnerabilities and agentic risk
PartnerStack operations have clear approval controls, but the required CLI can also change other agents’ installed skills without this skill explaining those effects.
Review and install the CLI separately before enabling this skill. Limit its automatic cross-agent skill changes; the publisher documents OO_SKILLS_SYNC_DISABLED=1 for disabling startup synchronization. Understand that OOMOL mediates your PartnerStack access, and verify customer-creation payloads before approving them. The remote installers and hosted connector were not audited.
The supplied command performs remote installer execution, not PartnerStack data operations. Nothing in the supplied chunk establishes this installer as a supporting dependency for the declared purpose. The downloaded script's contents are not provided, so its further behavior cannot be assessed.
The supplied code's sole behavior is a CLI login, rather than PartnerStack data operations. Authentication could be a supporting implementation detail if the CLI were established as a PartnerStack integration, but the supplied content provides no such connection.
Piping the HTTPS response directly into Bash executes mutable remote content without checking its integrity or reviewing it. The domain is consistent with the declared CLI provider, but compromise of that provider or its distribution infrastructure could turn this legitimate setup step into local arbitrary-code execution.
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 setup instructions direct the agent to execute downloaded shell or PowerShell scripts without an explicit installation approval step or artifact verification. Although installation is conditional on a missing CLI and serves a legitimate dependency, a compromised installer could execute arbitrary code with the agent's local privileges.
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