Security audit
Security checks for vulnerabilities and agentic risk
The Poper reading functions fit the stated purpose, but setup can execute unverified downloaded code and introduce broader persistent agent changes without clear user control.
Review and approve the CLI installation separately before enabling this skill. Check its bundled-skill installation and synchronization behavior, and limit Poper access to the needed account data. The complete skill text was inspected, but the remote installer and hosted connector implementations remain unverified. No artifact evidence establishes malicious intent.
The supplied chunk performs remote installation rather than searching or reading Poper data. Although installing a dependency can be a supporting implementation detail, this chunk establishes no relationship between the Oomol installer and the declared Poper functionality. The downloaded script's subsequent behavior cannot be determined from the supplied code.
Piping a mutable remote script directly into Bash executes its contents with the invoking user's privileges without integrity verification or review. Although the endpoint is relevant to the documented CLI dependency and uses HTTPS, compromise of the distribution infrastructure could turn routine setup into arbitrary code execution, including access to local files and credentials.
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
A missing CLI triggers instructions to execute downloaded code through Bash or PowerShell without first obtaining approval for software installation and local system changes. The conditional setup context reduces exposure, but a request to read Poper data does not itself authorize installing software or executing a remote installer.
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