Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

Worktree Codex Parallel

v1.1.4

使用 git worktree 隔离多个 Codex 实例,由 OpenClaw 主控器并行调度完成同一项目的不同编码模块。 适用场景:将一个编码项目拆分为独立子任务,让多个 Codex 实例并行实现,最后合并 PR。 触发条件:用户要求"多个 Codex 协作"、"并行编码"、"worktree 编码"、"多...

0· 344·0 current·0 all-time
byjiao yang@inuyashayang
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Suspicious
View report →
OpenClawOpenClaw
Suspicious
high confidence
!
Purpose & Capability
The skill's purpose (orchestrate multiple Codex agents using git worktrees) is coherent with the included scripts (setup_worktrees.sh, orchestrate.sh, push_and_pr.sh). However the SKILL metadata claims no required env/config paths while the instructions and code rely on several external binaries and secrets (OPENAI_API_KEY, CODEX_BIN, CLAUDE_BIN path, GH token). The skill does not declare these requirements in the registry metadata, which is inconsistent and surprising to a user.
!
Instruction Scope
SKILL.md and the scripts instruct the agent to read ~/.openclaw/openclaw.json for a GitHub token and to run Codex/Claude binaries with flags that can bypass sandboxing. Additionally, the dashboard's AI analysis thread (ai_analyze_async) reads the same ~/.openclaw file to extract OPENROUTER_API_KEY and posts log summaries to an external API (openrouter.ai). Those actions (reading a global OpenClaw config and transmitting log tails to a third-party) are outside the narrow 'worktree orchestration' description and are not declared.
Install Mechanism
No install spec is provided (instruction-only with bundled scripts and a dashboard). That minimizes installation-time risk because the skill does not fetch remote archives or run an installer. The risk is runtime behavior of the included scripts rather than an install-time downloader.
!
Credentials
The code accesses multiple credentials and config locations that are not declared: it expects OPENAI_API_KEY, CODEX_BIN, optional CLAUDE_BIN, and reads GH_TOKEN from ~/.openclaw/openclaw.json; the dashboard also extracts OPENROUTER_API_KEY from the same file. Requesting or reading another skill's/platform config file (~/.openclaw/openclaw.json) to obtain API keys is disproportionate and can lead to cross-skill secret access/exfiltration.
!
Persistence & Privilege
The skill does not set always:true and does not appear to persistently modify other skills, but it explicitly reads a platform/local config (~/.openclaw/openclaw.json) and extracts keys. Accessing and using other skills' config/credentials increases privilege and blast radius even though the skill itself isn't permanently installed as always:true.
What to consider before installing
This skill appears to implement parallel worktrees correctly, but it reads and uses secrets that are not declared and posts log data to an external service. Before installing or running: - Treat the dashboard and scripts as code that will run on your machine: review/modify them if you do not want automatic network calls. - Do not run dashboard.py or orchestrate.sh unless you are comfortable that ~/.openclaw/openclaw.json may be read; better: supply GH token and any API keys via environment variables instead of relying on that file. - The dashboard's ai_analyze_async reads OPENROUTER_API_KEY from your OpenClaw config and sends log tails (potentially code/content) to openrouter.ai. If you have sensitive code or secrets in logs, this can leak them. Remove or sandbox that feature, or require an explicit opt-in and an explicit environment variable for the analysis key. - The skill suggests using flags like --dangerously-skip-permissions / --dangerously-bypass-approvals-and-sandbox; those bypass host protections and increase risk. Avoid these unless you fully understand the implications. - Confirm the BASE URL (http://152.53.52.170:3003/v1) and any hardcoded IPs are intended and trustworthy — they point to a self-hosted proxy and could route model requests off your environment. If you still want to use this skill safely: require the owner to (1) declare required env vars in metadata, (2) stop reading ~/.openclaw/openclaw.json automatically (use explicit env vars), and (3) make external AI analysis optional and gated behind an explicit, purposeful opt-in.

Like a lobster shell, security has layers — review code before you run it.

latestvk970xefnmny14cjg0mjs0embe9827fec

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments