Security audit
Security checks for vulnerabilities and agentic risk
Carbone changes require approval, but the setup path can introduce broader changes to your agent environment that the skill does not explain.
Review setup before enabling this skill. Prefer a reviewed CLI release and decide whether to disable automatic skill synchronization before first use. Connecting Carbone entrusts OOMOL with its API credentials and requested operations. The skill provides clear approval rules for account changes, but its remote installers were unavailable for inspection; this review does not establish their full behavior.
The supplied command installs tooling from an Oomol endpoint rather than performing Carbone operations. Nothing in the supplied code establishes this installation as a supporting requirement for Carbone. The remote script's contents are not supplied, so its additional behavior cannot be determined.
The curl-to-bash command executes the current contents of a remote installer without pinning or independently verifying them. HTTPS protects transport but not against a compromised publisher or distribution service, which could deliver code that accesses local files and credentials or modifies the system; this is the same underlying installation risk identified by SQP-2.
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 execute remotely retrieved shell or PowerShell code without integrity verification or explicit approval for local software installation. A compromised distribution endpoint could execute arbitrary code with the invoking user's permissions; limiting setup to a missing-CLI error reduces exposure but does not prevent this risk.
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