Security audit
Security checks for vulnerabilities and agentic risk
The Kintone features fit the stated purpose, but setup directs the agent to execute downloaded code without verification or a clear approval step.
Review and approve CLI installation separately before allowing setup to run. Check any bundled agent-skill changes and connect only the Kintone account you intend OOMOL to access. The remote installer contents remain unverified; the review found no artifact-backed evidence of malicious intent.
The supplied chunk executes a remote installer and contains no Kintone search or read operations. Although dependency installation can be a supporting implementation detail, the supplied content establishes no connection between this installer and the declared Kintone functionality. The downloaded script's contents and additional effects cannot be determined from this chunk.
Piping a downloaded script directly into Bash executes mutable remote content with the agent process's local permissions, without prior inspection or independent integrity verification. HTTPS protects transport but does not prevent a compromised publisher or distribution endpoint from serving malicious code; the PowerShell alternative has the same weakness. The installation is conditional and uses the vendor's stated domain, which supports a legitimate purpose but does not eliminate 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 without first disclosing local changes or obtaining approval, expanding a Kintone read request into local code execution. Restricting setup to a missing-command error reduces exposure but does not establish user authorization to modify the environment; the declared Bash restriction may limit execution if enforced but is not a substitute for 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