Security audit
Security checks for vulnerabilities and agentic risk
This skill is a disclosed LinkPix image-generation integration; it installs and configures the expected CLI, but users should understand it may install Node/qhkit and upload supplied images to the service.
Install only if you are comfortable using the qhkit/LinkPix service, providing its API token, and sending selected prompt text or reference images to that service. Prefer a reviewed or pinned qhkit version in controlled environments, and be aware the skill may install Node/qhkit or update PATH if the runtime is missing.
The manifest says image-generation requests of many kinds 'must trigger', using broad mandatory language. Overly broad trigger conditions can cause the agent to invoke the skill in situations where user intent is ambiguous, increasing the chance of unintended tool execution, unnecessary package installation, token prompts, or external network access.
The trigger section includes a catch-all for 'free-form' uncovered generation/editing requests without clear negative examples or boundaries. This makes routing ambiguous and can over-expand tool use into adjacent tasks that may be better handled by other skills or by a non-tool response.
The skill instructs use of npx @iqinghu/qhkit without pinning an exact version, which makes execution depend on whatever package version is current at invocation time. This creates a supply-chain and reproducibility risk: a compromised or breaking upstream release could be fetched and executed unexpectedly in the agent environment.
This is a duplicate report of the same session-persistence behavior: installing binaries under the user's home directory and exporting PATH for continued use. Persistent tooling and PATH changes can outlive the session and expand the consequences of accidental or malicious later invocations.
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 is a duplicate report of the same session-persistence behavior: installing binaries under the user's home directory and exporting PATH for continued use. Persistent tooling and PATH changes can outlive the session and expand the consequences of accidental or malicious later invocations.
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"
The instruction says the CLI message is already user-facing Chinese and should be relayed directly, which effectively forces a specific language in user communication. There is no indication that the user can choose another language or that this locale restriction is optional.