Security audit
Security checks for vulnerabilities and agentic risk
Setup needs review because it can execute unverified downloaded code, and the required CLI may also change other installed agent skills.
Review and approve CLI installation separately instead of allowing the fallback commands to execute automatically. The installer contents and hosted connector implementation remain unverified. Confirm that OOMOL may handle your Mattermost connection and task data, and retain the skill's confirmation requirement before posting. Review the CLI's additional skill changes; current documentation provides OO_SKILLS_SYNC_DISABLED to disable startup synchronization. [CLI controls](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md#environment-variables)
The supplied code installs software from an Oomol endpoint rather than performing Mattermost operations. Although installation can be a supporting implementation detail, this chunk establishes no relationship between that installer and the declared Mattermost functionality. The downloaded script's contents and any further effects are not available for assessment.
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
- `create_post` — Create a Mattermost post in a channel. [write]
- `get_channel` — Retrieve one Mattermost channel by ID.
- `get_current_user` — Get the Mattermost user associated with the Personal Access Token.
- `get_team` — Retrieve one Mattermost team by ID.
- `list_channel_posts` — List Mattermost posts in a channel.
- `list_team_channels` — List public Mattermost channels in a team.
Piping a remotely fetched script directly into bash executes mutable third-party content without an opportunity to inspect it or verify an authenticated release. Compromise of the installer source could enable arbitrary code execution with the invoking user's permissions; HTTPS and the installer's legitimate role as a dependency do not eliminate that 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 setup fallback instructs execution of downloaded shell and PowerShell installers without explicit approval for local software installation or an explanation of the trust implications. Although conditional on a missing dependency, this expands a Mattermost task into local code execution with the invoking user's permissions; the declared tool restriction might block it in some environments but is not a safe installation design.
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
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
## Resources
- Mattermost homepage: https://mattermost.com
- API documentation: https://api.mattermost.com/