Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
codex-cn-bridge
v1.0.0Enable OpenAI Codex CLI to use domestic Chinese AI models via protocol conversion and auto-configuration with support for multiple providers.
⭐ 0· 263·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
The SKILL.md describes a Codex→Chinese-model protocol bridge (Qwen, Kimi, GLM) which is coherent with the skill name and description. However the registry metadata lists no required environment variables or install steps while the README clearly expects API keys and an installer; that mismatch suggests the metadata is incomplete or out of sync with actual behavior.
Instruction Scope
Runtime instructions are explicit and scoped to the bridge: create ~/.codex/, place a .env with provider API keys, run /codex-cn-bridge install/start/stop/test/exec and edit ~/.codex/cn-bridge/models.yaml. The instructions limit file access to the ~/.codex tree and Codex configuration (config.toml) and logs. There is no instruction to read unrelated system files, but the agent will be asked to modify Codex config and create files under the user's home directory.
Install Mechanism
The skill has no install spec in registry metadata (instruction-only). The SKILL.md recommends installing via the OpenClaw skills manager or cloning a GitHub repo (https://github.com/luckKiven/codex-cn-bridge.git). Downloading from GitHub is a standard approach, but because the registry did not embed an install package, following the instructions will download and execute external code at install/run time — inspect the repository before running any install/start commands.
Credentials
The registry lists no required environment variables, yet the SKILL.md explicitly instructs users to provide multiple provider API keys (QWEN_API_KEY, KIMI_API_KEY, ZHIPU_API_KEY) via ~/.codex/cn-bridge.env or environment variables. That mismatch is a red flag: the skill will request sensitive credentials not declared in metadata. Only provide the specific keys you intend the bridge to use and avoid sharing .env files.
Persistence & Privilege
The skill promises 'one‑click auto‑configure Codex' and lists a config.toml that will be 'automatically created'. That implies the installer or scripts will modify Codex CLI configuration (agent-level config) and write files under ~/.codex. The skill is not marked always:true, but automatic modification of another tool's configuration is a notable privilege that you should audit before allowing it.
What to consider before installing
This skill appears to do what it says (bridge Codex to Chinese providers), but there are discrepancies and privileges you should review before installing: 1) The registry metadata does not declare the API keys the documentation asks you to supply — expect to provide QWEN_API_KEY, KIMI_API_KEY, ZHIPU_API_KEY (and similar). 2) The SKILL.md instructs you to clone/run code from the project's GitHub repo and to run an install/start command that will create/modify files under ~/.codex and modify Codex's config.toml — inspect those scripts first. 3) Before running any install/start commands, manually review the repository (proxy.py, start scripts, install scripts, and any network calls) for unexpected behavior or secret exfiltration. 4) Keep the .env file local (do not commit it), and prefer creating a provider-specific key with minimal scope. 5) If you are unsure, run the installation in an isolated/test environment or container and verify what config changes are made. If you can provide the actual repository contents or an install script, I can re-evaluate with higher confidence.Like a lobster shell, security has layers — review code before you run it.
latestvk97a5hammwbg3m8af060340qmd82b0aq
License
MIT-0
Free to use, modify, and redistribute. No attribution required.