odoo-produce-video

odoo-produce-video is a command for Claude Code from Viindoo/odoo-mcp-client. It costs 104 tokens per session (779 once invoked), scanned A, original, MIT.

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.

In plain words
What is it for?
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.
Why use it?
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.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: mentions Codex.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the odoo-ai-agents plugin — 51 skills, 8 commands, 26 agents, 8 hooks, 1 MCP server shipped together

Good fit 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.

Compare 6 commands from other repositories ↓
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 51 skills, 8 commands, 26 agents, 8 hooks, 1 MCP server.

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.

agentmods badge for odoo-produce-video

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.

agentmods 80×15 button for odoo-produce-video

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 104 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 779 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00104 $0.00779
Opus 5 $0.00052 $0.00390
Sonnet 5 $0.00021 $0.00156
Haiku 4.5 $0.00010 $0.00078

Measured 11d ago against content hash 84246491a6a1, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, 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 11d 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 · 58 lines

How it starts

The opening of the file, as written. The whole thing — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/odoo-produce-video

This command is a thin dispatcher. All phase logic, gates, skill invocations, output paths, and fallback rules are defined in the declarative workflow SSOT:

plugins/odoo-ai-agents/workflows/video-produce.workflow.yaml

How to run

The workflow-chaining skill auto-discovers video-produce.workflow.yaml and executes it when this command fires. Dispatch happens via natural-language routing - the runner reads the workflow YAML and drives each phase in sequence.

To invoke: type /odoo-produce-video (optionally followed by a project label, e.g. /odoo-produce-video Sales-Demo-Q3). The runner collects remaining inputs interactively at Phase 0.

What the workflow produces

Three gated phases (Pipeline pattern):

Phase Handler Gate
0 - Storyboard inline approve / refine: [feedback] / cancel
1 - Record scenes odoo-demo-recording (per scene) approve / refine: [feedback] / cancel
2 - Assemble inline approve / skip / cancel

Gate replies are the two declared sets only (${CLAUDE_PLUGIN_ROOT}/snippets/planning-gate-contract.md), matching workflows/video-produce.workflow.yaml line for line. At Phase 1, refine: [scene numbers] re-takes just those scenes. At Phase 2, approve saves the assembled video and skip leaves it unsaved.

Output lands in <ISOLATE_DIR>/video/<project_label>-<YYYY-MM-DD>/ (resolve <SHARE_DIR>/<ISOLATE_DIR> once per ${CLAUDE_PLUGIN_ROOT}/snippets/state-root-resolution.md; substitute the captured absolute path - never write the placeholder or a bare .odoo-ai/ into a Read/Write/Edit).

pagecast is opt-in. Recording (pagecast / Playwright video) is no longer an eager browser MCP - only the headless chrome-devtools is eager. Wire the recorder family first via /odoo-ai-agents:odoo-setup browser (step 12 for Claude, step 10 for Codex/Gemini). If it is not wired, Phase 1 falls back to a chrome-devtools screenshot frame sequence assembled into a GIF.

Read the full file on GitHub · 58 lines

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. 11d 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 (7 stars, last pushed 5d ago), licensed MIT. It adds 104 tokens to every session and 779 once invoked, about $0.0005 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.