Most static alerts are false positives caused by Markdown code formatting, example paths, environment variable documentation, and expected vendor links. The pipe-to-shell installer and unquoted remote-manifest command substitution are confirmed risks. Automatic local-file uploads and social account actions also require explicit user awareness and approval.
The installation command executes remotely fetched content without giving the user an inspection or pinning step. A compromised endpoint could immediately run arbitrary shell commands.
The reinstall instruction again executes a mutable remote script directly in the shell. Transport security does not protect against a compromised publisher or distribution endpoint.
The documented command directly executes the response from a remote endpoint. Endpoint or supply-chain compromise would provide immediate shell execution.
The primary installation path downloads a mutable remote script and immediately executes it. A compromised service or release pipeline could run arbitrary commands in the user's account.
Consequential Social Account Actions Lack Confirmation Guidance
The skill can post content and advertises direct messages, follows, likes, and reposts. It does not require confirmation before these externally visible account actions.
The command example explicitly posts to Twitter, and the capability table lists other account-changing operations without an approval safeguard.
Supplying a local path causes the CLI to upload that file to inference.sh automatically. Sensitive files could leave the machine without a separate upload confirmation.
Both files explicitly state that local file paths are automatically uploaded instead of treated as URLs.
Capability review items (1)
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 command places unquoted output derived from a remote manifest into curl arguments. Malformed or compromised manifest content could alter the requested arguments despite the later checksum step.
Most static alerts are false positives caused by Markdown code formatting, example paths, environment variable documentation, and expected vendor links. The pipe-to-shell installer and unquoted remote-manifest command substitution are confirmed risks. Automatic local-file uploads and social account actions also require explicit user awareness and approval.
The installation command executes remotely fetched content without giving the user an inspection or pinning step. A compromised endpoint could immediately run arbitrary shell commands.
The reinstall instruction again executes a mutable remote script directly in the shell. Transport security does not protect against a compromised publisher or distribution endpoint.
The documented command directly executes the response from a remote endpoint. Endpoint or supply-chain compromise would provide immediate shell execution.
The primary installation path downloads a mutable remote script and immediately executes it. A compromised service or release pipeline could run arbitrary commands in the user's account.
Consequential Social Account Actions Lack Confirmation Guidance
The skill can post content and advertises direct messages, follows, likes, and reposts. It does not require confirmation before these externally visible account actions.
The command example explicitly posts to Twitter, and the capability table lists other account-changing operations without an approval safeguard.
Supplying a local path causes the CLI to upload that file to inference.sh automatically. Sensitive files could leave the machine without a separate upload confirmation.
Both files explicitly state that local file paths are automatically uploaded instead of treated as URLs.
Capability review items (1)
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 command places unquoted output derived from a remote manifest into curl arguments. Malformed or compromised manifest content could alter the requested arguments despite the later checksum step.
Most static hits are Markdown examples or documentation links, not executable skill code. The confirmed risk is installer guidance that pipes a remote script into sh, plus one manual install command that derives a download URL through shell substitution. I found no prompt-injection text or covert data-exfiltration instructions in the reviewed files.
The command pipes remote HTTPS content directly to sh as an installation step. A compromised endpoint or installer would execute arbitrary code on the user system.
The command pipes remote HTTPS content directly to sh as an installation step. A compromised endpoint or installer would execute arbitrary code on the user system.
The command pipes remote HTTPS content directly to sh as an installation step. A compromised endpoint or installer would execute arbitrary code on the user system.
The command pipes remote HTTPS content directly to sh as an installation step. A compromised endpoint or installer would execute arbitrary code on the user system.
Capability review items (1)
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 command evaluates a subshell that fetches a remote manifest and selects a download URL. This is installation guidance, but remote-controlled download selection is a supply-chain risk.
The skill documents useful inference.sh CLI workflows, but it includes multiple remote installer patterns that pipe downloaded content to a shell or derive binary downloads from a remote manifest. Several markdown backtick findings are false positives, but the confirmed risks include unsafe installation guidance, local file upload exposure, executable installation into the user PATH, and social media automation capabilities.
The command explicitly pipes a remote HTTPS response into sh. That pattern can execute arbitrary remote code during installation and should be blocked until replaced.
The reinstall command repeats the pipe-to-shell pattern. Re-running a mutable remote script without inspection or pinning is a critical supply-chain risk.
The installation command executes a remote script through sh without prior review. This is a direct pipe-to-shell pattern and a critical installer risk.
The skill prominently instructs curl -fsSL https://cli.inference.sh | sh. Directly executing a mutable remote installer is a critical publish-blocking pattern.
The skill states that local files are automatically uploaded when a path is provided, including images, audio, and media examples. An agent could expose sensitive local files if it follows these instructions without explicit user approval.
The documentation explicitly describes automatic local file uploads and gives multiple local path examples. This is an intentional capability with a clear data exposure risk.
The skill includes commands and related skills for posting to Twitter/X, sending DMs, following users, liking posts, and retweeting. These capabilities can enable spam, account abuse, or unauthorized public actions if used without explicit account-owner consent.
The cited lines directly list Twitter/X posting and automation actions. The abuse risk depends on account permissions, so confidence is high but not absolute.
Capability review items (19)
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 fenced command block contains curl piped to sh followed by login. The markdown label is noisy, but the command block includes a critical remote script execution instruction.
The URL is used in an installer command that downloads a remote script and pipes it to sh. This creates a remote code execution supply-chain risk if the endpoint or transport is compromised.
The documentation says parent-relative paths are accepted for local file uploads. That can cause unintended upload of files outside the working directory if an agent uses an unsafe path.
The manual install block includes shell commands that download binaries and place an executable in the user PATH. It also uses dynamic command substitution to choose the download URL.
The local file upload examples send local images, audio, and media paths to remote inference.sh apps. This is expected behavior, but it creates a real data exposure risk without explicit consent.
The command substitutes the result of a remote manifest request into a download command. A changed manifest or parsing issue can cause an unintended binary to be downloaded.
The manual install block includes command substitution that derives a binary URL from remote content. This is a risky installation pattern even though checksum verification is later suggested.
The command fetches a remote manifest and uses its parsed URL to download a binary. This network dependency directly controls which executable is installed.
The command moves a downloaded binary into ~/.local/bin, a hidden home-directory path commonly in PATH. That is a legitimate install location, but it installs an executable for future use.
> **Install the belt CLI skill:** `npx skills add belt-sh/cli`
The inline command asks the user to install another skill through npx. It is not Ruby execution, but it is a real external package and skill installation supply-chain risk.
This command block invokes the belt CLI to call remote AI apps, including a Twitter posting app. These are intended commands, but they can trigger external service actions from the agent.
| Run without waiting | `belt app run <app> --input input.json --no-wait` |
The command submits remote work without waiting for completion. It is intended usage, but it can start external processing before the user reviews the full result path.
The command writes into ~/.local/bin during manual installation. It is user-visible, but it still modifies a hidden home path with an executable artifact.
The command downloads checksum data from an external host as part of manual installation. This is expected but still creates a trust dependency on the remote distribution endpoint.
Most static hits are Markdown examples or documentation links, not executable skill code. The confirmed risk is installer guidance that pipes a remote script into sh, plus one manual install command that derives a download URL through shell substitution. I found no prompt-injection text or covert data-exfiltration instructions in the reviewed files.
The command pipes remote HTTPS content directly to sh as an installation step. A compromised endpoint or installer would execute arbitrary code on the user system.
The command pipes remote HTTPS content directly to sh as an installation step. A compromised endpoint or installer would execute arbitrary code on the user system.
The command pipes remote HTTPS content directly to sh as an installation step. A compromised endpoint or installer would execute arbitrary code on the user system.
The command pipes remote HTTPS content directly to sh as an installation step. A compromised endpoint or installer would execute arbitrary code on the user system.
Capability review items (1)
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 command evaluates a subshell that fetches a remote manifest and selects a download URL. This is installation guidance, but remote-controlled download selection is a supply-chain risk.