Security audit
Security checks for vulnerabilities and agentic risk
The skill requires approval for record changes, but its setup can execute unverified downloaded code and make broader agent-skill changes.
Review setup before installing. Prefer a verified CLI release installed separately, and disable automatic skill synchronization unless you want additional skills installed across your agents. Keep the explicit approval requirements for record changes and deletions, and consider OOMOL's access to sensitive client data. Remote installer contents and server-side credential controls were not verified; no malicious behavior was established.
The declared purpose concerns Credit Repair Cloud data management, but the supplied command executes an Oomol installer without showing any connection to that purpose. No evidence establishes this installation as a supporting dependency. The remote script's contents and further effects cannot be determined from the supplied chunk.
The command pipes a mutable remote script directly into Bash without a pinned version or independently verified integrity; the PowerShell alternative has the same execution pattern. If the distribution endpoint or release pipeline is compromised, attacker-controlled code could execute with the invoking user's permissions and access local files or credentials; HTTPS and the legitimate dependency relationship do not eliminate that supply-chain risk.
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 directs the agent to install software by executing downloaded code without first explaining the system changes or requesting installation approval. Restricting this to a missing-CLI error reduces exposure, but authorization to manage Credit Repair Cloud records does not necessarily authorize local software installation.
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