Security audit
Security checks for vulnerabilities and agentic risk
The Adafruit IO workflow is coherent, but setup executes unverified downloaded code and leaves persistent agent changes insufficiently disclosed.
Review and install a verified CLI release yourself before use. Decide whether its automatic agent-skill installation and synchronization are acceptable, and disable synchronization if unwanted. Understand that OOMOL mediates account access and feed operations, and retain the required write confirmations. The remote installers' exact contents remain unverified; no malicious intent is established.
The supplied command installs external CLI software instead of performing an Adafruit IO operation. Nothing in the supplied content establishes this installer as a supporting dependency for the declared functionality. The downloaded script's contents are unavailable, so its further behavior cannot be determined.
Authentication could support the declared purpose, but it is the entirety of the supplied code. No Adafruit IO integration or data-handling behavior is shown, so the implemented primary behavior does not substantiate the declared functionality.
Piping an HTTPS response directly into Bash executes mutable remote content without a pinned version or independently verified integrity. HTTPS protects transport but does not prevent a compromised distribution endpoint or installer from running malicious code on the local machine; this is the same underlying installation risk highlighted 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 missing-CLI fallback directs execution of downloaded shell or PowerShell code without requiring review, integrity verification, or explicit approval for local system changes. Although installing a dependency is relevant to this skill and occurs only conditionally, a compromised installer could execute arbitrary code with the invoking user's privileges.
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