virtual-couple-travel-vlog

Pass

Audited by Gen Agent Trust Hub on Sep 11, 2026

Risk Level: SAFEINDIRECT_PROMPT_INJECTIONCOMMAND_EXECUTIONDATA_EXFILTRATIONDYNAMIC_EXECUTION
Full Analysis
  • [INDIRECT_PROMPT_INJECTION]: The skill ingests untrusted user input such as the 'vlog theme' and 'destination' which are then interpolated into complex multi-step prompts for image and video generation tools.
  • Ingestion points: SKILL.md (Task 0
  • Intake) and README.md intake instructions.
  • Boundary markers: Absent; there are no delimiters or 'ignore embedded instructions' warnings around the interpolated user content.
  • Capability inventory: The skill has significant local capabilities including writing files to the disk and executing shell commands via subprocess (ffmpeg, npx, node, python scripts).
  • Sanitization: None detected; user inputs are directly placed into prompt templates in references/prompts.md.
  • [COMMAND_EXECUTION]: Multiple scripts (scripts/assemble-vlog.py, scripts/run-topview-omni.py) utilize subprocess.run to execute external binaries like ffmpeg and node. While these are used for intended project functionality (video editing and assembly), they represent a broad attack surface if user input were to influence the command arguments.
  • [DATA_EXFILTRATION]: The script scripts/check-video-providers.py programmatically checks for the presence of numerous sensitive API keys in environment variables (e.g., SEEDANCE_API_KEY, KREA_API_KEY, LOVART_API_KEY, LIBTV_API_KEY). While this is used for capability detection to inform the user, these environment variables contain highly sensitive credentials.
  • [DYNAMIC_EXECUTION]: The script scripts/run-topview-omni.py dynamically constructs a command to execute a Python script (video_gen.py) whose path is determined at runtime by checking environment variables (TOPVIEW_SKILL) or searching common home directory locations. This allows for the execution of code from paths outside the skill's own directory.
  • [PRIVILEGE_ESCALATION]: The README.md and references/tooling.md documentation suggest a 'Chrome Runtime Fix' that involves manually copying and renaming the Chrome executable within the user's profile cache. While documented as a compatibility fix for the HyperFrames tool, such instructions could be leveraged to misplace executables in sensitive paths.
Audit Metadata
Risk Level
SAFE
Analyzed
Sep 11, 2026, 05:27 PM