Security audit
Security checks for vulnerabilities and agentic risk
The Gitee features fit the stated purpose, but setup can execute unverified remote installers without first obtaining your approval.
Review the setup behavior before installing. Install a reviewed CLI version yourself and require approval before the agent downloads or executes installers. Check which Gitee permissions you grant OOMOL and whether the CLI installs additional agent skills. The bundled skill contains no demonstrated malicious payload, but its remote installers could not be inspected. The clean static scan does not resolve that uncertainty.
The supplied command runs a remote installer rather than searching or reading Gitee data. Nothing in the supplied chunk establishes that this installation is a supporting dependency for the declared functionality. The remote script's contents and effects are not available for assessment.
Piping a remotely fetched script directly into Bash executes mutable remote code with the agent process's privileges, without a pinned version or independent integrity verification. Compromise of the installer distribution path could enable credential theft or arbitrary local changes; HTTPS and the missing-CLI condition do not eliminate this supply-chain risk, and the PowerShell alternative has the same issue.
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 when the CLI is missing without requiring user approval or explaining local system changes. A request to read Gitee data does not itself authorize installing software, and the setup context limits when this happens but does not establish consent.
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