Security audit
Security checks for vulnerabilities and agentic risk
The skill is coherently about AI video generation, but its documentation asks users to run mutable remote installers and unpinned package commands that could execute unreviewed code.
Review before installing. Prefer a pinned, inspectable CLI installation path with independently published checksums or signatures, avoid running the pipe-to-shell command from a privileged shell, and do not submit sensitive prompts, media, private URLs, or account credentials unless you accept inference.sh and model-provider processing. Treat the optional related-skill npx commands as separate installations that need their own review, especially Twitter automation.
SKILL.md:17Remote Installer Executed Directly Through a Shell Pipeline
SKILL.md:152Unpinned Third-Party Skill and Package Retrieval
The documentation instructs users to execute a remote script directly with curl ... | sh, which is a classic unsafe pattern because it runs code fetched over the network without prior inspection. If the hosting endpoint, TLS trust chain, DNS, or upstream distribution is compromised, users could immediately execute attacker-controlled shell code.
# Install CLI
curl -fsSL https://cli.inference.sh | sh && infsh login
# Generate a video with Veo
infsh app run google/veo-3-1-fast --input '{"prompt": "drone shot flying over a forest"}'
The trigger list includes broad phrases such as 'video generation', 'generate video', and 'ai animation', which are likely to match many normal user requests. Overbroad activation can cause unintended invocation of a skill that sends prompts and media to external services, increasing privacy and misuse risk.
The skill does not clearly warn that prompts, images, audio, and video URLs are transmitted to third-party infrastructure for processing. Users may unknowingly disclose sensitive content, proprietary media, or internal URLs to external services, which is especially relevant for a media-generation workflow.
The skill recommends running npx skills add ... without pinning an exact package version, which means users may retrieve whatever version is current at execution time. This creates a supply-chain risk because a compromised or malicious future package release could be executed unexpectedly.
This npx skills add ... invocation is unpinned and therefore subject to version drift and package supply-chain compromise. Even if the current package is safe, later releases could introduce malicious code or breaking behavior that users execute automatically.
Using npx skills without a pinned version causes the command to resolve dynamically at runtime, exposing users to malicious updates or dependency hijacking. In a skill-distribution context, this is a meaningful supply-chain weakness rather than a purely theoretical issue.
Because this npx skills add ... example is not pinned, users may execute a different package state than the author tested. That undermines reproducibility and opens the door to executing malicious or compromised package content from the registry.
An unpinned npx invocation is a real supply-chain risk because it delegates trust to the latest available package resolution. If an attacker compromises the package, namespace, or dependency chain, users following the documentation could execute attacker-controlled code.
This command again relies on npx without an immutable version, making execution dependent on external package state at the time the user runs it. In documentation intended for broad use, repeated unpinned examples increase exposure to registry and dependency compromise.
No suspicious patterns detected.