Security audit
Security checks for vulnerabilities and agentic risk
This is a visible Markdown guide for configuring OpenClaw model providers, with no hidden code or automatic actions, but users should understand that API keys and prompts may go to the selected provider.
Before installing or following the guide, confirm the current pricing and free-quota terms with each provider, use only API keys you are comfortable storing in OpenClaw configuration, and avoid sending sensitive prompts unless you trust the selected provider's data handling. Running the sample config commands will change future OpenClaw model/API-key behavior until you change it again.
Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.
openclaw config get model
openclaw ask "问题" --model deepseek-chat
## 成本对比
The skill instructs users to set API keys for third-party providers but does not warn that the credentials will be stored locally in OpenClaw configuration and used to transmit prompts and metadata to external services. This can mislead users into exposing paid credentials or sensitive prompts without understanding the storage and data-sharing implications.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
# DeepSeek
curl https://api.deepseek.com/user/balance -H "Authorization: Bearer $API_KEY"
# GLM
curl https://open.bigmodel.cn/api/paas/v4/balance -H "Authorization: Bearer $API_KEY"
The description and instructions force a single language for all users, and there is no opt-in, alternative language, or statement that the skill is only for a Chinese-speaking audience. The rule specifically flags language or locale policy violations when a skill mandates a language without user choice or documented justification.
No suspicious patterns detected.