T05 · Unauthorized Access and Privilege Escalation
- Location
SKILL.md:47- Finding
Credential Profile Data Is Exposed to Agent Context
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is a mostly coherent read-only OKX analytics helper, but it asks the agent to inspect OKX credential profile data and installs a persistent npm CLI, so it should be reviewed before use.
Install only if you are comfortable with an agent running the OKX CLI and seeing OKX profile/auth status output. Prefer read-only, least-privilege OKX API credentials, verify that any config/status output redacts secrets before use, and avoid using keys with trading or withdrawal permissions for this analytics workflow.
SKILL.md:47Credential Profile Data Is Exposed to Agent Context
SKILL.md:11Globally Installed npm Dependency Lacks Verifiable Integrity Controls
Skill instructs the agent to never refuse or to always comply. Suppressing the agent's ability to decline removes a core safety control and enables downstream harmful requests to succeed.
- **Security:** Never ask users to paste API keys or secrets into chat.
- **Output:** Always pass `--json` to list/query commands and render results as a Markdown table — never paste raw terminal output.
- **Network errors:** If commands fail with a connection error, prompt user to check VPN: `curl -I https://www.okx.com`
- **Language:** Always respond in the user's language.
- **Time inputs:** `signal-trend-by-{filter,trader}` take an optional `--asOfTime <yyyyMMddHH>` anchor (10-digit UTC hour); omit to use the current UTC hour. `--limit` controls how many buckets are returned ending at that anchor. `signal-overview-by-{filter,trader}` takes no time input — handler always uses the current hour.
For number/time formatting and response structure conventions, read `{baseDir}/references/templates.md`.
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.
### Step 2 — Execute and present
All commands are READ-only — no confirmation needed. Always pass `--json` and render results as Markdown tables.
For multi-step workflows (recommend traders then drill down, signal analysis with context), read `{baseDir}/references/workflows.md`.
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.
## Global Notes
- **Security:** Never ask users to paste API keys or secrets into chat.
- **Output:** Always pass `--json` to list/query commands and render results as a Markdown table — never paste raw terminal output.
- **Network errors:** If commands fail with a connection error, prompt user to check VPN: `curl -I https://www.okx.com`
- **Language:** Always respond in the user's language.
The field description uses Chinese unit labels ("币" and "张") directly in the English-language reference, effectively imposing a specific locale in the skill documentation. This can violate language/locale policy when no user choice or explicit regional justification is provided.
The workflow repeatedly presents user invocations as fixed Chinese/English example phrases, but the document does not state that the skill should respect the user's preferred language or offer a language choice. Under the policy rule, forcing a specific language or locale without opt-in can be a natural-language policy issue.
No suspicious patterns detected.