Borrowing it
Nothing to install: this file belongs to jordanurbs/venice-video-harness. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/jordanurbs/venice-video-harness/main/.agents/commands/generate-trailer.mdgit clone --depth 1 https://github.com/jordanurbs/venice-video-harnessWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/jordanurbs/venice-video-harness/generate-trailer)<a href="https://agentmods.dev/commands/jordanurbs/venice-video-harness/generate-trailer"><img src="https://agentmods.dev/badge/commands/jordanurbs/venice-video-harness/generate-trailer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/jordanurbs/venice-video-harness/generate-trailer"><img src="https://agentmods.dev/badge/commands/jordanurbs/venice-video-harness/generate-trailer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.01585 |
| Opus 5 | $0.00000 | $0.00792 |
| Sonnet 5 | $0.00000 | $0.00317 |
| Haiku 4.5 | $0.00000 | $0.00159 |
Grade A, and why
generate-trailer scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/generate-trailer
Analyze the screenplay and generate a curated trailer -- selecting the most compelling moments, generating panel images, and creating video clips.
Usage
/generate-trailer --project <project-dir> --duration <1m|3m>
Arguments
--project: Project output directory (required)--duration: Trailer length --1mfor 1-minute teaser (10-15 shots) or3mfor 3-minute theatrical (25-40 shots). Default:1m--model: Video model to use (optional, default:kling-o3-pro-image-to-video). Options:kling-o3-pro-image-to-video,vidu-q3-image-to-video,veo3.1-fast-image-to-video
What This Does
Phase 1: Screenplay Analysis
- Load
project.jsonand read all scene data - Analyze the dramatic arc: world, inciting incident, protagonist journey, central tension
- Identify the most visually striking and emotionally resonant moments
- Follow the trailer-curator agent's methodology (see
.agents/agents/trailer-curator.md)
Phase 2: Shot List Curation
- Select 10-15 shots (1m) or 25-40 shots (3m) from across the screenplay
- For each shot, determine:
- Scene source and specific moment
- Shot composition (type, camera, framing)
- Duration in the trailer
- Audio layer (dialogue, SFX, ambient)
- Whether an existing storyboard panel can be reused
- Arrange shots into the trailer's pacing structure:
- 1m: Atmosphere (slow) -> Intrigue (medium) -> Escalation (fast) -> Title
- 3m: Status Quo -> Inciting Incident -> Rising Stakes -> Cliffhanger -> Title
- Save the shot list as
output/<project>/trailer/trailer-plan.json - Present the shot list to the user for review before generating
Phase 3: Panel Generation
- Create
output/<project>/trailer/directory - For shots that reuse existing panels: symlink or copy from
scene-NNN/ - For new shots: generate via Venice API using:
- The project's locked aesthetic profile
- Full character descriptions from character locks
nano-banana-promodel,1Kresolution,16:9aspect ratio
- Save as
shot-T01.png,shot-T02.png, etc. - Generate corresponding
shot-TNN.video.jsonfor each panel
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 12d ago First seen · 143 lines · 0 tokens per session scan A 072819df4016
generate-trailer is a command published in the GitHub repository jordanurbs/venice-video-harness (30 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,585 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.