Security audit
Security checks for vulnerabilities and agentic risk
The Zammad workflow has clear approval controls, but automatic setup executes unchecked remote code and may change other installed agent skills.
Review and install a verified CLI release separately before using this skill, and review its automatic skill synchronization settings. Connect only the Zammad permissions you need and confirm ticket changes. OOMOL mediates account access; its hosted connector and the downloaded installer are outside the reviewed artifact.
The supplied chunk performs remote installer execution rather than Zammad operations. Nothing in the chunk establishes that this installer is a supporting dependency for the declared Zammad functionality. The installer's contents and further effects are not provided and cannot be determined from this snippet.
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
- `create_ticket` — Create a Zammad ticket with its initial text article. [write]
- `create_ticket_article` — Add a text article to an existing Zammad ticket. [write]
- `get_current_user` — Retrieve the Zammad user associated with the connected access token.
- `get_ticket` — Retrieve one Zammad ticket by ID.
- `list_ticket_articles` — List articles belonging to a Zammad ticket.
- `list_tickets` — List tickets visible to the connected Zammad user.
The fallback installation command streams a mutable remote script directly into Bash without version pinning or independent integrity verification; the PowerShell alternative has the same issue. If the distribution endpoint or release infrastructure is compromised, attacker-controlled code would run with the invoking user's privileges and could access local data or credentials. Restricting installation to a missing-CLI error reduces exposure frequency but does not make execution safe.
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
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