Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add commands/moore-developers/grok-cli/video-editgit clone --depth 1 https://github.com/Moore-developers/grok-cliWhat 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 | $0.00000 | $0.00485 |
| Opus 5 | $0.00000 | $0.00243 |
| Sonnet 5 | $0.00000 | $0.00097 |
| Haiku 4.5 | $0.00000 | $0.00049 |
Grade A, and why
video-edit 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 2d 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.
What it actually says
grok-cli video-edit
Purpose
Edit an existing video with Grok Imagine.
This command is separate from video. video handles text-to-video, image-to-video, and reference-image video; video-edit handles editing an existing MP4 video.
Common Usage
grok-cli video-edit --video-url https://example.com/source.mp4 --prompt "Give the woman a silver necklace"
Use a local video file:
grok-cli video-edit --video ./source.mp4 --prompt "Give the woman a silver necklace"
Script or skill usage:
grok-cli video-edit --json --video-url https://example.com/source.mp4 --prompt "Make the scene more cinematic"
Parameters
PROMPT: positional edit prompt.--prompt <PROMPT>: explicit script-friendly prompt.--video-url <URL>: source video URL to edit.--video <PATH>: local source video path to edit.--json: use the standard JSON envelope.--auth-file <PATH>: override the OAuth state file path.--model <MODEL>: override the model for this video edit request only.--timeout <SECONDS>: total video polling timeout, default600; individual HTTP requests still stay within the media request ceiling.
Behavior
- Default model is
grok-imagine-video. - The command calls
POST /videos/editsand sendsvideo: {"url": ...}. - Local videos are encoded as data URIs before being sent as
video.url. - The command does not send
duration,aspect_ratio, orresolution; the edited output inherits the input video properties. - It reads
request_idfrom the create response and then pollsGET /videos/{request_id}until completion. - Successful calls are written to the local usage SQLite database under video usage.
JSON Fields
data contains:
providercredential_sourcemodelvideomodalitydurationextra.request_id
modality is fixed to edit.
Related Docs
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.
- 2d ago First seen · 65 lines · 0 tokens per session scan A 053b13003db1
video-edit is a command published in the GitHub repository Moore-developers/grok-cli (52 stars, last pushed 19d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 485 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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
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.