The skill is transparent about using the inference.sh CLI, but several install instructions use curl-to-shell and remote binary installation patterns. Most API-key and documentation-link findings are false positives, while external CLI execution, hosted-app data transfer, and Twitter/X automation remain real risks.
The primary install instruction executes remote shell content with sh. This is a critical supply-chain risk if the endpoint or transport is compromised.
The skill includes examples for x/post-tweet and lists Twitter/X actions such as posting, direct messages, follows, likes, and retweets. These actions can affect a public account when run with authenticated credentials.
The cited lines explicitly show x/post-tweet and Twitter/X automation commands. Misuse depends on credentials, but the business action is clear.
The skill routes prompts and input files to hosted apps such as image, video, LLM, search, and 3D services through infsh app run. This can expose user content to the selected app provider.
The examples show remote app execution with prompts, and the references state that outputs are returned through cloud URLs. The behavior is intended but privacy-relevant.
Capability review items (22)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
The referenced manual install block contains shell commands that download, verify, extract, and install a remote binary. It is documented setup, but it still executes external commands on the user system.
The quick examples contain infsh app run commands that send prompts to hosted AI apps. This is intended behavior, but it is real external command execution.
The manual install block includes shell substitution and several shell commands. It is legitimate installation guidance, but it raises command execution risk.
The command writes into a hidden home-directory path used for local executables. This is expected installation behavior, but it changes user executable search paths.
The hardcoded URL is used in an installer command that retrieves remote shell content. The network endpoint is expected, but it is security-relevant because it controls the script source.
The Markdown image embeds a remote cloud.inference.sh asset. It is not code execution, but rendering the skill can trigger a third-party network request.
The skill is transparent about using the inference.sh CLI, but several install instructions use curl-to-shell and remote binary installation patterns. Most API-key and documentation-link findings are false positives, while external CLI execution, hosted-app data transfer, and Twitter/X automation remain real risks.
The primary install instruction executes remote shell content with sh. This is a critical supply-chain risk if the endpoint or transport is compromised.
The skill includes examples for x/post-tweet and lists Twitter/X actions such as posting, direct messages, follows, likes, and retweets. These actions can affect a public account when run with authenticated credentials.
The cited lines explicitly show x/post-tweet and Twitter/X automation commands. Misuse depends on credentials, but the business action is clear.
The skill routes prompts and input files to hosted apps such as image, video, LLM, search, and 3D services through infsh app run. This can expose user content to the selected app provider.
The examples show remote app execution with prompts, and the references state that outputs are returned through cloud URLs. The behavior is intended but privacy-relevant.
Capability review items (22)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
The referenced manual install block contains shell commands that download, verify, extract, and install a remote binary. It is documented setup, but it still executes external commands on the user system.
The quick examples contain infsh app run commands that send prompts to hosted AI apps. This is intended behavior, but it is real external command execution.
The manual install block includes shell substitution and several shell commands. It is legitimate installation guidance, but it raises command execution risk.
The command writes into a hidden home-directory path used for local executables. This is expected installation behavior, but it changes user executable search paths.
The hardcoded URL is used in an installer command that retrieves remote shell content. The network endpoint is expected, but it is security-relevant because it controls the script source.
The Markdown image embeds a remote cloud.inference.sh asset. It is not code execution, but rendering the skill can trigger a third-party network request.
Static analysis flagged many command and network patterns, but most are markdown examples for the documented infsh CLI rather than executable code. Confirmed concerns are the remote installer piped to sh, authenticated cloud execution, API key configuration, and minor filesystem writes for shell completion; no prompt injection or malicious exfiltration intent was found.
5
Files scanned
554
Lines analyzed
10
Review items
0
False positives ignored
Capability review items (6)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
The documentation instructs users to download an installer from a remote URL and pipe it directly to sh. This is a supply-chain risk because a changed endpoint, compromised transport path, or compromised host could execute arbitrary installer code before local review.
The pipe-to-shell pattern is directly present in installation examples. The surrounding documentation offers a manual install path and checksum discussion, so this is a real but not clearly malicious risk.
The skill is designed to run hosted inference.sh apps over the network using the local infsh CLI. This is expected behavior, but prompts, files, generated outputs, and Twitter/X actions may leave the local environment depending on the selected app.
The skill purpose and examples clearly involve network execution of remote apps. The behavior is legitimate for this skill, but users need to understand data disclosure and side-effect risks.
The documentation tells users to configure INFSH_API_KEY for CI/CD and notes that it overrides local config. This is normal authentication guidance, but exposed environment variables could allow unauthorized use of the account.
The files explicitly document an API key environment variable. There is no evidence the skill reads or exfiltrates the key itself, so the risk is credential handling rather than malicious behavior.
Most external command findings are CLI examples inside documentation. They are not executable skill code, and the declared tool permission is limited to Bash(infsh *), but the examples still guide users to run commands with cloud side effects.
The flagged lines are fenced markdown command examples and command tables. Context strongly supports false positives for direct code execution inside the skill.
Checksum References Misclassified as Weak Cryptography
Static analysis flagged weak cryptography, but the reviewed content references SHA-256 checksum verification for downloaded binaries. This is a safety control, not a weak cryptographic algorithm use in skill code.
The clearest reviewed occurrence is SHA-256 checksum documentation. Some analyzer line mappings point at tables, so there is no evidence of implemented weak cryptography.
The CLI reference includes shell completion examples that write generated completion files under system or user shell configuration paths. This is common CLI setup behavior, but users should review paths before running commands.
The filesystem writes are visible in documentation examples and are limited to installation or shell completion paths. There is no evidence of hidden persistence or arbitrary file modification.
This is a documentation skill for the inference.sh CLI platform. All static findings are false positives - the skill contains only documentation with CLI examples. The allowed-tools restriction to Bash(infsh *) limits execution to the official inference.sh CLI only. Network access is to inference.sh API endpoints, and credential handling is through standard CLI authentication.