Security audit
Security checks for vulnerabilities and agentic risk
The Appstle data-reading features fit the stated purpose, but setup can execute unverified downloaded code and introduce broader agent changes without clear approval.
Review the setup before installing. Install a reviewed CLI version yourself, control whether it installs or synchronizes other agent skills, and connect only the Appstle account needed. OOMOL mediates access to customer data. The concern is setup authority and under-disclosed changes; the inspected skill does not establish malicious intent.
The supplied code performs remote software installation, not Appstle data searching or reading. Nothing in the chunk connects this installer to the declared Appstle functionality, so it cannot be treated as merely a demonstrated supporting implementation detail. The downloaded script's further behavior is not visible.
Piping an HTTPS response directly into bash executes mutable remote code without independently verifying its integrity or reviewing it first. A compromised installation endpoint or release pipeline could execute attacker-controlled commands with the invoking user's privileges; the legitimate dependency context and missing-CLI condition narrow exposure but do not remove this 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 missing-CLI fallback directs installation through remotely fetched shell or PowerShell code without requiring informed approval or explaining that installation executes code and changes the local environment. Its conditional placement and the declared Bash(oo *) tool restriction reduce immediate execution exposure, but neither makes the documented installation procedure safe if a user or more broadly privileged agent follows it.
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