Security audit
Security checks for vulnerabilities and agentic risk
The Humaans features fit the stated purpose, but setup can execute unverified software with broader effects on your agent environment.
Review the CLI setup before installing. Use a reviewed, version-pinned installation and explicitly control whether it may install or synchronize other agent skills; the publisher documents controls in its [command reference](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md). Grant only needed Humaans read scopes and consider OOMOL's access to employee data. The entire bundled skill was inspected, but the remote installers were unavailable for inspection; no malicious behavior was established.
The supplied code performs remote installer execution, not the declared Humaans data operations. Nothing in the supplied chunk establishes that installing Oomol is a supporting dependency for Humaans access. The downloaded script's contents and further effects cannot be determined from this chunk.
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
## Available actions
- `get_current_person` — Retrieve the Humaans person record that owns the current API access token using public:read or private:read access.
- `get_person` — Retrieve one Humaans person by identifier using public:read or private:read access.
- `get_token_info` — Retrieve the scopes granted to the current Humaans API access token.
- `list_people` — List Humaans people with common exact-match filters and offset pagination using public:read or private:read access.
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
- `get_current_person` — Retrieve the Humaans person record that owns the current API access token using public:read or private:read access.
- `get_person` — Retrieve one Humaans person by identifier using public:read or private:read access.
- `get_token_info` — Retrieve the scopes granted to the current Humaans API access token.
- `list_people` — List Humaans people with common exact-match filters and offset pagination using public:read or private:read access.
## Safety
The curl-to-Bash pipeline immediately executes mutable remote content without a pinned version or integrity verification. HTTPS protects transport but does not protect against a compromised publisher or distribution infrastructure, which could result in local code execution and access to files or credentials available to the process; this is the same underlying installation risk identified 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 setup instructions pipe downloaded scripts directly into Bash or PowerShell without verifying their integrity or requiring explicit approval for local software installation. A compromised distribution endpoint could therefore execute arbitrary code with the agent's local privileges; the missing-command condition reduces exposure but does not establish trust.
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