The documentation contains repeated remote installer commands that pipe live content to a shell, plus an unsafe manifest-driven download command. It also enables local file uploads and public social media actions without explicit consent controls; most other alerts are Markdown or documentation false positives.
The command pipes an uninspected network response directly into sh. A compromised server, DNS path, or changed installer can execute arbitrary commands.
The update guidance again executes remote shell content without local inspection or pinning. This is a direct remote code execution supply-chain pattern.
The documented installation command executes a live remote response through sh. There is no opportunity to verify the retrieved script before execution.
The primary setup flow executes downloaded shell text without review, version pinning, or prior signature verification. This can yield arbitrary local code execution.
Automatic Local File Upload Can Expose Sensitive Data
The CLI automatically uploads any supplied local path to the hosted service. The skill provides no path allowlist, sensitivity check, or explicit upload confirmation.
Both files explicitly state that local paths are uploaded and show absolute, relative, and home-directory inputs. The missing consent and scope controls are visible in the reviewed guidance.
Public Social Media Actions Lack Confirmation Controls
The examples can publish posts and media to Twitter or X, but the skill does not require a preview or user confirmation before consequential account changes.
The cited commands explicitly post text and media to an external account. No confirmation requirement appears around either example.
Capability review items (8)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
> **Install the belt CLI skill:** `npx skills add belt-sh/cli`
Although the backticks are Markdown, the documented npx command installs a separate unpinned community skill. Executing it expands the trust boundary beyond the reviewed files.
The unquoted substitution derives curl arguments from a remote manifest through fragile text parsing. A changed or compromised manifest can redirect the binary download or inject curl options through word splitting.
The URL supplies a remote installer whose response is executed immediately. HTTPS does not protect against a compromised origin or unsafe installer update.
The command downloads checksums used to trust an executable from the same vendor origin. Origin compromise can therefore replace both the binary and its checksum.
The remote manifest determines which executable archive curl downloads. The URL is not pinned, and its output is consumed through unquoted command substitution.
The skill appears to be legitimate documentation for the inference.sh CLI, with no prompt injection or malicious override language found. Confirmed risks include remote pipe-to-shell installation, downloading binaries into the user PATH, automatic local file uploads to cloud services, and social media actions with external side effects.
The skill explains that local paths are automatically uploaded when used as inputs. This can expose sensitive media or documents if users pass unintended paths.
Both files explicitly state automatic uploads and show local image, audio, and media paths. This is an intentional data-transfer behavior, not only path syntax.
The skill includes Twitter/X actions for posts, direct messages, follows, likes, and retweets. These commands can create public or account-affecting side effects.
The file names concrete Twitter/X write actions, including posting and direct messages. This is clear external side-effect behavior even when user-authorized.
Capability review items (11)
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 manual install moves a downloaded executable into ~/.local/bin, which commonly affects the user PATH. That is an expected install step but security sensitive.
The manual install pipeline uses shell command substitution to choose a binary URL from a remote manifest. It is an intentional shell pattern with supply-chain risk.
The command writes into a hidden home-directory path used for local executables. It is legitimate installation behavior but can persist a downloaded binary.
> **What does the installer do?** The [install script](https://cli.inference.sh) detects your OS and
The prose links directly to the remote installer and describes binary download behavior. This is a low-severity external dependency, not a standalone exploit.
The manual install instructions fetch checksums from dist.inference.sh. It is expected installer traffic, but still security relevant for binary trust.
The skill appears to be legitimate documentation for the inference.sh CLI, with no prompt injection or malicious override language found. Confirmed risks include remote pipe-to-shell installation, downloading binaries into the user PATH, automatic local file uploads to cloud services, and social media actions with external side effects.
The skill explains that local paths are automatically uploaded when used as inputs. This can expose sensitive media or documents if users pass unintended paths.
Both files explicitly state automatic uploads and show local image, audio, and media paths. This is an intentional data-transfer behavior, not only path syntax.
The skill includes Twitter/X actions for posts, direct messages, follows, likes, and retweets. These commands can create public or account-affecting side effects.
The file names concrete Twitter/X write actions, including posting and direct messages. This is clear external side-effect behavior even when user-authorized.
Capability review items (11)
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 manual install moves a downloaded executable into ~/.local/bin, which commonly affects the user PATH. That is an expected install step but security sensitive.
The manual install pipeline uses shell command substitution to choose a binary URL from a remote manifest. It is an intentional shell pattern with supply-chain risk.
The command writes into a hidden home-directory path used for local executables. It is legitimate installation behavior but can persist a downloaded binary.
> **What does the installer do?** The [install script](https://cli.inference.sh) detects your OS and
The prose links directly to the remote installer and describes binary download behavior. This is a low-severity external dependency, not a standalone exploit.
The manual install instructions fetch checksums from dist.inference.sh. It is expected installer traffic, but still security relevant for binary trust.
Static analysis flagged many shell, network, credential, and filesystem patterns. Review found these are mostly documentation examples for the infsh CLI, but the skill still carries medium risk because it encourages pipe-to-shell installation, cloud execution, local file uploads, and API-key based authentication. No prompt injection attempt or confirmed malicious intent was found.
5
Files scanned
596
Lines analyzed
9
Review items
2
False positives ignored
Capability review items (5)
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 skill recommends installing and reinstalling the CLI with curl piped directly to sh. This is a real supply chain risk because a remote script is executed immediately, even though the documentation also provides manual checksum guidance.
The pipe-to-shell command is explicitly present in multiple installation snippets. It appears to be legitimate documentation, not malicious code, so the risk is medium rather than critical.
The skill is designed to run cloud-hosted AI apps through infsh commands. User prompts, task inputs, generated media requests, and search queries may be sent to inference.sh or third-party app providers.
The network behavior is core to the skill and is clearly documented through infsh app and task commands. This is expected functionality, but users must understand that data leaves the local environment.
The documentation states that local file paths are automatically uploaded when supplied as app input. This can expose local images, audio, video, screenshots, or other files if an agent runs a command with sensitive paths.
The local upload behavior is described directly and examples include absolute, relative, and home-directory paths. The risk is user-mediated but real because the skill enables file transfer to cloud services.
The skill documents INFSH_API_KEY for CI and troubleshooting. This is a normal authentication pattern, but it can expose credentials if commands, logs, or prompts reveal environment values.
The API key references are documentation for legitimate authentication. There is no evidence of exfiltration, but API key handling is security-sensitive.
Shell Command Examples Are Mostly Expected CLI Usage
Most external command findings are Markdown examples showing infsh usage, app discovery, task polling, completions, and related skill installation. These are expected for a CLI skill and do not show arbitrary command execution beyond the allowed infsh command scope.
The flagged lines are documentation snippets rather than hidden scripts. The declared tool scope is Bash(infsh *), which limits direct execution to the infsh CLI.
Static false positives ignored (2)
These static matches were dismissed by semantic review or matched schema-only tokens, so they are shown for transparency but do not drive the quality score.
The scanner reported weak cryptography, but the reviewed context refers to SHA-256 checksum verification and ordinary app or model names. I found no evidence of MD5, SHA-1, or custom cryptographic code being used for protection.
The static labels do not match the reviewed Markdown context. Confidence is moderate because the findings are broad line-level heuristics, but no weak algorithm use was visible.
Reviewed files do not contain text that claims system authority, tells the evaluator to ignore instructions, or asks the assistant to skip security review. No prompt injection finding is confirmed.
The files contain ordinary frontmatter and Markdown documentation. I did not find suspicious override language or fake system messages.
Static analysis flagged 203 patterns across 5 files (596 lines), but all findings are false positives. The detected 'external_commands' are markdown documentation showing CLI usage examples, not actual code execution. URLs are legitimate service endpoints. The curl|sh installation pattern is standard for CLI tools. Network access to inference.sh APIs is the intended functionality. Environment variable usage for API keys follows security best practices.
The skill uses the infsh CLI tool which executes shell commands. This is inherent to the skill's purpose of running AI inference via command line. Users should verify the CLI source and understand it will make network requests to inference.sh APIs.
The CLI supports uploading local files by accepting file paths in input parameters. Users should only provide files they intend to upload to the inference service.
Capability review items (2)
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 skill makes HTTP requests to inference.sh and related domains (cli.inference.sh, dist.inference.sh, cloud.inference.sh). This is expected behavior for a cloud AI inference client.
The skill stores authentication credentials locally after login and supports INFSH_API_KEY environment variable. This is standard practice for CLI authentication.