Security audit
Security checks for vulnerabilities and agentic risk
The Dida365 actions have clear approval rules, but setup directs the agent to run unverified downloaded code without separate installation approval.
Review and approve CLI installation separately, preferably using a verified, pinned release. OOMOL will handle your connected Dida365 account. Review the CLI's automatic skill synchronization before use; its documented OO_SKILLS_SYNC_DISABLED setting can disable those writes. Installer contents and remote connector behavior were not verified. Continue requiring approval for exact account changes and deletion targets.
The supplied chunk performs remote installer execution rather than any visible Dida365 operation. Installation can be a supporting implementation detail, but this chunk provides no evidence connecting the Oomol installer to the declared Dida365 functionality. The downloaded script's contents and downstream effects are not available for assessment.
The curl-to-bash command immediately executes mutable remote content without pinning a version or independently verifying its integrity; the PowerShell alternative has the same issue. HTTPS protects transport but does not protect against a compromised distribution endpoint, which could deliver code that accesses local files or alters the host under the invoking user's privileges.
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 setup directs the agent to execute a remote installer without explaining its host-system effects or requiring approval for installation. Although limited to a missing dependency, this can turn an ordinary Dida365 request into execution of downloaded code with the user's privileges, outside the confirmation rules for Dida365 writes.
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