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.
git clone --depth 1 https://github.com/Poppify/poppify-claude-pluginWrote 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/poppify/poppify-claude-plugin/troubleshoot)<a href="https://agentmods.dev/commands/poppify/poppify-claude-plugin/troubleshoot"><img src="https://agentmods.dev/badge/commands/poppify/poppify-claude-plugin/troubleshoot.svg" alt="Measured on agentmods" 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.00024 | $0.00340 |
| Opus 5 | $0.00012 | $0.00170 |
| Sonnet 5 | $0.00005 | $0.00068 |
| Haiku 4.5 | $0.00002 | $0.00034 |
Grade A, and why
troubleshoot 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 7d 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
The user is reporting a problem with a Poppify render. Args: $ARGUMENTS
Invoke the poppify-troubleshoot skill and walk the user through:
-
Identify the symptom — match the user's description to one of these categories:
- No audio in finished video
- Caption text wrong color
- Captions missing on some slides
- Caption position wrong
- Render failed / seeds charged but no video
- Video URL doesn't open
- Duration wrong
- Image looks wrong (or has text baked in)
- Library search returned nothing
-
Apply the corresponding action from the skill's decision tree. Most fixes are one tool call + re-
confirm. -
Verify the fix — if your client has a shell with ffmpeg,
/poppify:verify-rendergives a deep check; otherwise just re-get_resultand confirm the reported symptom is gone (e.g. audio now attached, text finalized). Verification is optional, not a gate. -
If the symptom doesn't match any category, file via
submit_feedback({ apiKey, sessionId, frictionPoints: ["<the symptom + what you tried>"] })— there is nokind/descriptionfield; bugs go infrictionPoints.
Do NOT re-flag issues already listed in the MCP server's "Recently addressed" block — they're known-resolved.
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.
- 7d ago First seen · 28 lines · 24 tokens per session scan A d09b15cb4604
troubleshoot is a command published in the GitHub repository Poppify/poppify-claude-plugin (0 stars, last pushed 1mo ago), licensed MIT. It adds 24 tokens to every session and 340 once invoked, about $0.0001 per session on Opus 5. 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-31.
Other commands, from other repositories
setup
Set up PromptCut - installs deps (pip, ffmpeg), checks keys, CapCut folder.
video
Make a full video from an idea or a script - storyboard, voiceover, images, music, subtitles, render.
premiere
Hand the video to Adobe Premiere Pro - editable sequence with motion keyframes, voiceover, music, titles, SRT subtitles.
resolve
Hand the video to DaVinci Resolve - editable timeline with zoom/position keyframes, voiceover, music, titles, SRT subtitles.
shorts
Cut vertical shorts or reels - from a topic, a script, or an existing long video.
vegas
Hand the video to VEGAS Pro - a script builds the project with pan/crop keyframes, voiceover, ducked music, titles, markers.