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/tommymorgan/claude-plugins/demogit clone --depth 1 https://github.com/tommymorgan/claude-pluginsWrote 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/tommymorgan/claude-plugins/demo)<a href="https://agentmods.dev/commands/tommymorgan/claude-plugins/demo"><img src="https://agentmods.dev/badge/commands/tommymorgan/claude-plugins/demo.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 | $0.00017 | $0.00670 |
| Opus 5 | $0.00009 | $0.00335 |
| Sonnet 5 | $0.00003 | $0.00134 |
| Haiku 4.5 | $0.00002 | $0.00067 |
Grade A, and why
tommymorgan:demo 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 4d 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Demo Video
Create an automated product demo video with natural voice narration.
Usage
/tommymorgan:demo— Start a conversational demo creation session/tommymorgan:demo <plan-file>— Generate demo from a plan file's Demo Scenarios section
Workflow
Step 1: Determine Demo Parameters
If a plan file path is provided:
- Read the plan file
- Extract the "Demo Scenarios" section
- Generate the demo script automatically without user interaction
If no plan file is provided:
- Ask the user one question at a time:
- What product/feature are you demoing?
- What's the URL to start from?
- Who's the audience? (marketing / technical / both)
- Which recording strategy? (scene-based / continuous / screenshot)
- Target duration? (30s / 1min / 2min / custom)
Step 2: Generate Demo Script
Generate a structured demo script with scenes based on the user's description.
Present the script scene-by-scene for approval:
Scene 1: "<title>"
Narration: "<text>"
Actions: <list>
Scene 2: "<title>"
Narration: "<text>"
Actions: <list>
The user can edit narration text, reorder scenes, or add/remove scenes.
Sensitive content check: If any scene navigates to a URL requiring authentication, warn:
⚠️ This demo targets authenticated URLs. The recording may capture sensitive
data (user info, tokens, private content). Review the final video before sharing.
Step 3: Write Script to Disk
Write the finalized script using the demo orchestrator:
cd <project>/demos/<name>
node <plugin-root>/demo/dist/script-io.js write
The script is saved to <project>/demos/<name>/script.json.
Step 4: Execute Recording Pipeline
Run the four-stage pipeline:
- Check dependencies — Verify ffmpeg and browser tools are available
- Record scenes — Using the selected strategy (scene-based / continuous / screenshot)
- Generate narration — Edge TTS for each scene's narration text
- Compose video — ffmpeg combines video + audio + transitions into MP4
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.
- 4d ago First seen · 94 lines · 17 tokens per session scan A 51888e24c1a0
tommymorgan:demo is a command published in the GitHub repository tommymorgan/claude-plugins (4 stars, last pushed 1mo ago), licensed MIT. It adds 17 tokens to every session and 670 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
brand-generate
Generate an on-brand document from a saved Brand Profile.
stt
Transcribe a local audio file or remote audio URL into text.
audition-voices
Generate voice audition samples for a character using Venice TTS.
music-suno-prompt
Grounded Suno prompt synthesis from local knowledge corpus + persona canon + label canon. No vibes-prompting.
tag
Add or remove free-form tags on photos, then find them with search --tag.
develop-image-prompt.eval
Generates a detailed image generation prompt from a document or content description. Good output: a prompt that is specific, visual, non-abstract, includes style/composition/lighting guidance, and is calibrated to the specified dimensions and style options.