ffmpeg
Pass
Audited by Gen Agent Trust Hub on Sep 13, 2026
Risk Level: SAFECOMMAND_EXECUTIONINDIRECT_PROMPT_INJECTION
Full Analysis
- [COMMAND_EXECUTION]: The skill includes several utility scripts (e.g.,
scripts/ffmpeg-preflight,scripts/audio-inspect,scripts/media-intake, andscripts/extract-review-frames) that executeffmpegandffprobebinaries via Python'ssubprocess.runandsubprocess.Popen. - These executions are performed using list-based arguments rather than shell strings, effectively preventing shell injection vulnerabilities.
- The scripts implement robust security controls, including execution timeouts, non-mutating inventory probes, and hard limits on output size (e.g.,
MAX_OUTPUT_BYTES_HARDinscripts/media-intakeandMAX_DIAGNOSTIC_BYTESinscripts/extract-review-frames). - [INDIRECT_PROMPT_INJECTION]: The skill identifies an attack surface for indirect prompt injection as it is designed to process untrusted data, specifically local media files and transcript JSON artifacts.
- Ingestion points: Data enters the workflow through tools like
scripts/audio-inspect(via the--transcriptargument) andscripts/media-intake(via file path scanning). - Boundary markers: The
SKILL.mdinstructions mandate the use of explicit evidence classes (e.g., "Editorial heuristic" vs. "Observed artifact") and require a "needs_review" status for all editorial decisions. Templates likeedit-decision-list.jsoninclude confidence and review status fields to maintain transparency. - Capability inventory: The skill possesses capabilities for file writing, frame extraction, and subprocess execution.
- Sanitization: The skill follows best practices for sanitization, such as
scripts/vision-review-handoffwhich uses opaque asset IDs to prevent leaking private paths, andscripts/render-edlwhich includes a dedicatedescape_ffconcat_pathfunction to sanitize paths in generatedffconcatfiles. - [SAFE]: The skill demonstrates a high degree of security maturity. It emphasizes non-negotiable safety checks, explicit stream selection, and the use of private workspaces for sensitive operations. It explicitly forbids the interpretation of identity, intent, or whole-program meaning from technical metadata alone, forcing human-in-the-loop verification for consequential editorial claims.
Audit Metadata