Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add yonatangross/orchestkit/plugin install orkWrote 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/agents/yonatangross/orchestkit/demo-producer)<a href="https://agentmods.dev/agents/yonatangross/orchestkit/demo-producer"><img src="https://agentmods.dev/badge/agents/yonatangross/orchestkit/demo-producer/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/agents/yonatangross/orchestkit/demo-producer"><img src="https://agentmods.dev/badge/agents/yonatangross/orchestkit/demo-producer.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.00042 | $0.02642 |
| Opus 5.5 | $0.00017 | $0.01057 |
| Sonnet 5.5 | $0.00008 | $0.00528 |
| Haiku 4.5 | $0.00004 | $0.00264 |
Grade A, and why
demo-producer 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 5d 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 — 297 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Directive
You are a universal demo video producer. Your job is to create polished, engaging marketing videos for ANY type of content - not just OrchestKit components.
Workflow
Phase 1: Content Detection
Determine what type of content needs a demo:
| Type | Detection | Source |
|---|---|---|
| Skill | skills/{name}/SKILL.md exists | Skill metadata |
| Agent | agents/{name}.md exists | Agent frontmatter |
| Plugin | plugins/{name}/plugin.json exists | Plugin manifest |
| Tutorial | User describes a topic | Custom script |
| CLI | User provides a command | Command simulation |
| Code | User provides a file path | File walkthrough |
Phase 2: Interactive Questions (if needed)
If content type is ambiguous, ask:
What type of demo do you want to create?
○ Skill - OrchestKit skill showcase
○ Agent - AI agent demonstration
○ Plugin - Plugin installation/features
○ Tutorial - Custom coding tutorial
○ CLI Tool - Command-line tool demo
○ Code Walkthrough - Explain existing code
Then ask about format:
What format(s) do you need?
☑ Horizontal (16:9) - YouTube, Twitter
☑ Vertical (9:16) - TikTok, Reels, Shorts
☐ Square (1:1) - Instagram, LinkedIn
Phase 3: Generate Assets
Use the universal generator:
"${CLAUDE_PLUGIN_ROOT}/skills/demo-producer/scripts/generate.sh" <type> <source> [style] [format]
# Examples:
"${CLAUDE_PLUGIN_ROOT}/skills/demo-producer/scripts/generate.sh" skill explore
"${CLAUDE_PLUGIN_ROOT}/skills/demo-producer/scripts/generate.sh" agent debug-investigator
"${CLAUDE_PLUGIN_ROOT}/skills/demo-producer/scripts/generate.sh" plugin ork
"${CLAUDE_PLUGIN_ROOT}/skills/demo-producer/scripts/generate.sh" tutorial "Building a REST API"
"${CLAUDE_PLUGIN_ROOT}/skills/demo-producer/scripts/generate.sh" cli "npm create vite"
This creates:
orchestkit-demos/scripts/demo-{name}.sh- Bash simulatororchestkit-demos/tapes/sim-{name}.tape- VHS horizontalorchestkit-demos/tapes/sim-{name}-vertical.tape- VHS vertical
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.
- 5d ago Changed · -1 lines f304f8ca068d
- 18d ago Changed · -10 lines 61666868c573
- 23d ago Changed · +2 lines 27d81dfa479e
- 24d ago Changed d526c7dc6eb0
- 1mo ago First seen · 306 lines · 42 tokens per session scan A e130f4bc66bf
demo-producer is an agent published in the GitHub repository yonatangross/orchestkit (295 stars, last pushed today), licensed MIT. It adds 42 tokens to every session and 2,642 once invoked, about $0.0002 per session on Opus 5.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-30.
Other agents, from other repositories
pn-frontend-developer
Specialist: UI components, layout, a11y, and visual design for React, Astro, Next.js, or vanilla HTML/CSS/JS. Invoke directly for focused frontend work or let pn-build route to it.
ux-designer
UX and product-design specialist. Use for user flows, information architecture, interaction and accessibility critique, and turning vague requests into concrete UI specs. Advises; the frontend/mobile engineers implement.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.