verify-render

A command for checking a rendered Poppify vertical video before it is published. It downloads the video, checks its technical streams and duration, and inspects sample frames for requested visual details.

In plain words
What is it for?
Use it to verify a Poppify video URL or session result, including its format, frame rate, duration, captions, caption color, and caption placement.
Why use it?
It helps catch missing audio or video, incorrect dimensions or timing, and visible caption mistakes before sharing the render.

Command

Install

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.

agentmods
npx agentmods add commands/poppify/poppify-claude-plugin/verify-render
Clone the repo
git clone --depth 1 https://github.com/Poppify/poppify-claude-plugin
Per session 27 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 434 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00027 $0.00434
Opus 5 $0.00014 $0.00217
Sonnet 5 $0.00005 $0.00087
Haiku 4.5 $0.00003 $0.00043

Measured yesterday against content hash 5ab9cc4733e6, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

verify-render scanned grade A with 1 finding 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 yesterday.

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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

**Capability gate first.** This is an OPTIONAL deep check that needs a local shell with `ffmpeg` + `ffprobe` + `curl`. If your client has no Bash/shell tool (e.g. Claude Desktop, web), STOP — you can't run it. Just give
commands/verify-render.md · 30 lines

What it actually says

The user wants to verify a Poppify render before shipping the URL. Args: $ARGUMENTS

Capability gate first. This is an OPTIONAL deep check that needs a local shell with ffmpeg + ffprobe + curl. If your client has no Bash/shell tool (e.g. Claude Desktop, web), STOP — you can't run it. Just give the user the videoUrl and, if they've reported a problem, use /poppify:troubleshoot (pure MCP-tool reasoning, no shell). Only proceed if which ffprobe ffmpeg curl succeeds.

Invoke the poppify-render-debug skill and follow it:

  1. If args is a sessionId, call get_result({ sessionId, apiKey }) to fetch the videoUrl. If args is already a URL, use it directly.

  2. Download the MP4 to /tmp/poppify-verify/render.mp4.

  3. Run ffprobe -v error -print_format json -show_streams -show_format and check:

    • Video stream present (h264, 720x1280, ~24fps)
    • Audio stream present (aac)
    • Duration matches the sum of per-slide durations (text-length-driven; voiceover/live clips play in full) within ±1s
  4. Extract sample frames at 1fps and visually verify:

    • Caption text appears on intended slides
    • Caption color matches request
    • Caption position matches textAnimation
    • Image content matches the slide's voiceoverShort
  5. Produce a Markdown verdict table. Green checks → hand the URL to the user (signed URL valid ~7 days). Red checks → surface the specific failure and recommend the corresponding /poppify:troubleshoot path.

  6. Clean up /tmp/poppify-verify/ when done.

Changes

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.

  1. yesterday First seen · 30 lines · 27 tokens per session scan A 5ab9cc4733e6

Subscribe to this mod's changes

verify-render is a command published in the GitHub repository Poppify/poppify-claude-plugin (0 stars, last pushed 1mo ago), licensed MIT. It adds 27 tokens to every session and 434 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.