Security audit
Security checks for vulnerabilities and agentic risk
The Passcreator workflow is coherent, but its setup fallback can execute remote installation code without separate user approval.
Review the setup fallback before enabling this skill. Prefer installing a verified CLI yourself, and require approval before software installation or changes to other agent skills. OOMOL mediates Passcreator account operations. The bundled workflow requires confirmation for writes, but the external installers were unavailable for inspection.
The supplied chunk performs no visible Passcreator operations. Its sole action executes an installer from a different service, with no demonstrated connection to Passcreator. Although dependency installation can be a supporting implementation detail, the supplied content provides no evidence of that relationship. The downloaded script's further behavior cannot be determined from this chunk.
Piping a remotely fetched installer directly into bash executes mutable external code without an independent integrity check or review; the PowerShell alternative has the same weakness. HTTPS protects transport but not against a compromised distribution endpoint, which could deliver code running with the agent process's local permissions; the missing-CLI prerequisite and any enforced tool restrictions reduce exposure.
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 fallback instructs the agent to install software after a missing-command error without requiring approval or explaining the resulting system changes. Although conditional and related to a legitimate prerequisite, it can expand a Passcreator data request into local code execution and persistent environment changes; the declared oo-only tool restriction may limit execution if enforced.
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