Security audit
Security checks for vulnerabilities and agentic risk
The skill matches its image-generation purpose, but it asks agents to install and update external command-line tools globally and may persist changes to the user's shell environment.
Review this skill before installing if you do not want agents to install global npm packages, fetch Node binaries, modify PATH behavior, or upload product images to qinghu services. Prefer a pinned, preinstalled qhkit in a contained environment and provide tokens only for the account and site you intend to use.
The metadata says this skill 'must trigger' for broad, common requests related to product scene images, with no limiting conditions or competing-skill boundaries. In an agentic system, overbroad mandatory triggering can cause inappropriate tool invocation, unintended external calls, or bypass of safer/manual handling paths.
The 'when to trigger' examples are illustrative but ambiguous, and they do not define precise boundaries for when the skill should not run. That ambiguity increases the chance of accidental activation for ordinary conversations or adjacent requests, leading to unnecessary tool use and possible data disclosure to external services.
The skill instructs use of npx @iqinghu/qhkit without pinning an exact version, which allows execution of whatever package version is current at invocation time. In a security-sensitive agent environment, this creates supply-chain risk and makes behavior non-reproducible; a compromised or breaking upstream release could execute arbitrary code or alter outputs.
This duplicated finding points to the same persistent install-and-PATH-modification behavior. Persisting user-space binaries and shell-path changes can silently alter later command resolution and expand the blast radius of any compromised dependency or misconfiguration beyond the immediate task.
cd /tmp && curl -fsSLO https://nodejs.org/dist/v22.22.3/node-v22.22.3-linux-x64.tar.xz cd /tmp && curl -fsSL https://nodejs.org/dist/v22.22.3/SHASUMS256.txt | grep ' node-v22.22.3-linux-x64.tar.xz$' | sha256sum -c - mkdir -p "$HOME/.local/lib" && tar -xJf /tmp/node-v22.22.3-linux-x64.tar.xz -C "$HOME/.local/lib" export PATH="$HOME/.local/lib/node-v22.22.3-linux-x64/bin:$PATH"
This duplicated finding points to the same persistent install-and-PATH-modification behavior. Persisting user-space binaries and shell-path changes can silently alter later command resolution and expand the blast radius of any compromised dependency or misconfiguration beyond the immediate task.
cd /tmp && curl -fsSLO https://nodejs.org/dist/v22.22.3/node-v22.22.3-linux-x64.tar.xz cd /tmp && curl -fsSL https://nodejs.org/dist/v22.22.3/SHASUMS256.txt | grep ' node-v22.22.3-linux-x64.tar.xz$' | sha256sum -c - mkdir -p "$HOME/.local/lib" && tar -xJf /tmp/node-v22.22.3-linux-x64.tar.xz -C "$HOME/.local/lib" export PATH="$HOME/.local/lib/node-v22.22.3-linux-x64/bin:$PATH"
Several instructions assume or require Chinese output to the user, such as relaying the CLI message "原样转告用户" and stating those messages are already user-facing Chinese. This imposes a specific language/locale behavior without documenting user opt-in or offering an alternative language choice.