Skills/ClawHub/varg-video-prompting

varg-video-prompting@1.0.10

CAUTION· static only

Publisher claims: "How to prompt varg's video, image, voice and music models so shots come out right on the first or second take: the working loop (references, look bible, environment master, character sheets, approved stills, audio lock, animate, QA), which model for which shot (Seedance 2.5, Kling 4, Veo 3.1, Wan 3, Nano Banana 2.1, GPT Image 2.5, ElevenLabs v4, Lyria, lip sync), prompt anatomy for video, stills and edits, what @image1, @video1 and @audio1 references copy, dialogue and voice rules, a frame and audio QA checklist, and gotchas from paid runs. Use when someone asks to "prompt Seedance", write a Kling or Veo prompt, pick a "varg video model" or asks "which model", does "image to video" or "video to video", needs a "consistent character" or location, makes "storyboard stills" or key frames, wants dialogue or lip sync, or asks why a clip looks like AI slop, drifted or ignored the prompt." Observed in sandbox: static analysis only — behavior not yet observed.

Registry ClawHubPublisher vargai · publishing for 215 daysInstalls 181Last detonated 30 h ago
What would fix thisWatchDispute verdict

Coverage

Static only; nothing was run yet.

The label rests on the code, the instruction files and the publisher. The honeypot run replaces this verdict when it completes.

Is [email protected] safe to install?

KillerSkills analysed it statically (a sandbox run is pending) on 2026-11-13 and scored it 64/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: HTML comment carrying imperative instructions to the agent. Summary: static analysis only — behavior not yet observed.

Behavior trace

Queued for honeypot run · static analysis only
t+CategoryObserved action

This version has not been detonated yet. The score above counts behavior as unknown (50/100), so it cannot read Verified until the honeypot run completes and replaces this verdict.

Static findings

CRITICAL
HTML comment carrying imperative instructions to the agentREADME.md:1 · HTML comment carrying imperative instructions to the agentGenerated by .github/readme/build.ts from SKILL.md files and .github/readme/*.json. Edit those and run `bun .github/readme/build.ts`; CI fails when this file isFix: Keep SKILL.md to visible, descriptive text. Remove comments and encoded text that address the agent.
AST01

No other findings across 1,518 lines in 8 files.

Cost to the agent

Instructions loaded
≈8,151 tok
1 file · 8 in bundle

Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.

Known vulnerabilities

Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.

What would make this Verified

16 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%
  1. Unclaimed publisher≈ +8 on the totalClaim vargai: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
  2. Hidden instructions≈ +6 on the totalRemove HTML comments, zero-width characters and white-on-white text that carry instructions. Everything the agent is meant to read should be visible to the person reading the file.
Publish a new version to ClawHub, then queue it here. Not your skill? Claim the handle to get verdict changes by email.Claim vargaiPropose a patch to the maintainer