What is odoo-produce-video?

A workflow for making a multi-scene demonstration video of Odoo. It plans the scenes, records each click path, and combines the recordings into one MP4 video or GIF.

Use it to create demonstrations with several Odoo screens or processes, such as a three-scene sales demo. It helps prepare the storyboard, record scenes, and assemble the final deliverable.

It gives a structured process for turning a product walkthrough into a finished video. Approval points let you review or refine the storyboard and recordings as the work progresses.

odoo-produce-video — Command for Claude Code by Viindoo

Install

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.

Claude Code

/plugin marketplace add Viindoo/odoo-mcp-client

Claude Code

/plugin install odoo-ai-agents

Made for: Claude Code.

Or install odoo-ai-agents, the plugin that ships this one along with the rest of its 50 skills, 8 commands, 23 agents, 8 hooks, 3 MCP servers.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/viindoo/odoo-mcp-client/odoo-produce-video/github.svg)](https://agentmods.dev/commands/viindoo/odoo-mcp-client/odoo-produce-video)

Your own site

<a href="https://agentmods.dev/commands/viindoo/odoo-mcp-client/odoo-produce-video"><img src="https://agentmods.dev/badge/commands/viindoo/odoo-mcp-client/odoo-produce-video/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/viindoo/odoo-mcp-client/odoo-produce-video"><img src="https://agentmods.dev/badge/commands/viindoo/odoo-mcp-client/odoo-produce-video.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 15 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 635 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00015	$0.00635
Opus 5.5	$0.00006	$0.00254
Sonnet 5.5	$0.00003	$0.00127
Haiku 4.5	$0.00002	$0.00064

Measured 9d ago against content hash 80e357884c85, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

odoo-produce-video 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 9d 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.

plugins/odoo-ai-agents/commands/odoo-produce-video.md · 43 lines

What it actually says

/odoo-produce-video

Thin dispatcher. Invoke the workflow-chaining skill with plugins/odoo-ai-agents/workflows/video-produce.workflow.yaml; the workflow holds every phase (storyboard, record-scenes, narrate, assemble, publish), its scripts and its paths. $ARGUMENTS is an optional project label (e.g. /odoo-produce-video Sales-Demo-Q3); the runner collects the remaining inputs before the workflow plan.

The storyboard is the plan, approved once at the gate with its rendering and the AI cost estimate; the other phases then run in the odoo-video-producer agent without stopping, except for a budget overrun, a key field on screen, a failed verification or a narration line a human must listen to. Everything lands under <ISOLATE_DIR>/video/<project_label>/ (resolve <ISOLATE_DIR> once per ${CLAUDE_PLUGIN_ROOT}/snippets/state-root-resolution.md); the deliverables per language under deliverables/<lang>/.

Prerequisites, each with its setup step: the recorder (/odoo-ai-agents:odoo-setup browser installs the pinned Playwright library and Chromium and runs the recorder's self-test); a spoken narration (/odoo-ai-agents:odoo-setup voice: the speech endpoint, a voice per language, the speech-to-text check); publishing to YouTube (/odoo-ai-agents:odoo-setup youtube: the channel per purpose). Without the recorder a scene is recorded through odoo-demo-recording's browser MCP path, without automatic pacing.

languages decides the narration: one video per language, its own recording with the UI in that language, captions, thumbnail, description with chapters, YouTube-spec MP4; no language = a silent video. A scene that calls an AI feature declares its cost in the storyboard's ai block (key only as the NAME of a dedicated environment variable; a shared key is refused), the plan shows the estimate, and the run stops when the spend passes it by the margin.

destination, asked when not given: youtube or youtube:<purpose> publishes to the channel of that purpose (docs for user guides, the docs site and the App Store page's video block; marketing for sales and marketing videos) after the youtube_check for that purpose passed, the key scan is clean and the operator approved the "listen" lines; pr attaches the preview to a pull request; none keeps the files under the run directory.

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.

9d ago Changed · -3 lines 80e357884c85
16d ago Changed · +9 lines f6e153f295de
17d ago Changed · +7 lines 4cfe6c1872b8
20d ago Changed · -29 lines a4472c9c7fa8
1mo ago Changed · -89 tokens per session 543de1da31cb
1mo ago Changed · +1 lines 537b90fea15c
2mo ago First seen · 58 lines · 104 tokens per session scan A 84246491a6a1

Subscribe to this mod's changes

odoo-produce-video is a command published in the GitHub repository Viindoo/odoo-mcp-client (9 stars, last pushed 2d ago), licensed MIT. It adds 15 tokens to every session and 635 once invoked, about $0.0001 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-31.

Creative and media

odoo-produce-video next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
odoo-produce-videoViindoo/odoo-mcp-client	Command	9	2d ago	MIT	A	15	Claude Code
checklistgithub/spec-kit	Command	149k	today	MIT	A	13	Claude Code
clarifygithub/spec-kit	Command	149k	today	MIT	A	27	Claude Code
specifygithub/spec-kit	Command	149k	today	MIT	A	13	Claude Code
convergegithub/spec-kit	Command	149k	today	MIT	A	35	Claude Code
implementgithub/spec-kit	Command	149k	today	MIT	A	14	Claude Code
speckit.bug.fixgithub/spec-kit	Command	149k	today	MIT	A	12	Claude Code