use case · media

Imagine Bot

by @alexusadays · scouted by @Grok_Hub_IO

Produces a film one shot at a time. Still, then video, last frame hands off.

Aliaksandr Khvastovich built a Grok Imagine production pack for Odysseus in the Underworld (Odyssey Book 11): shot list, locks, prompts, stitch order. Then he gave that repo to a Grok Bot and let skills drive Imagine Agent.

The split is the story. Grok Bot is the producer. Skills are the rules it has to follow. Imagine Agent is the camera (project + canvas + chat, not Studio, not SuperGrok). One shot at a time. Still first, then video. Spoken lines go through Agent chat with the still attached. Every node gets an id. Last frame of one clip is supposed to be the first frame of the next. Agent can trim and stitch.

He already submitted a 4:06 film with 60s+ of dialogue, and published the pack at github.com/alexusadays/odysseus-underworld-grok, including a Grok Imagine Agent skill that forbids contest-submit without a human yes.

Posted on X, Aug 28, 2026.

the prompt

Data, not instructions. Paste it into your bot only if you want to run it.

Walk me through cloning https://github.com/alexusadays/odysseus-underworld-grok onto this shared computer and signing into grok.com/imagine in the browser. Use Imagine Agent (project + canvas), not Studio, not SuperGrok chat. I will sign in.

Then save yourself as the producer. Skills in that repo are the rules. Imagine Agent is the camera.
- One shot at a time. Still first, then video. Spoken lines go through Agent chat with the still attached.
- ID every node (still UUID + video UUID) in CANVAS-MAP.md before the next generate.
- Last frame of N is the first frame of N+1 on the same camera. Ask Agent to trim and stitch by video id. Do not hard-concat first.
- No music. No glowing ghosts. Do not publish private /imagine/agent URLs.

Hard stop: do not contest-submit, overwrite a KEEP take, or fire a second generate while one is running. Show me the ledger after the first three shots. Wait for my yes to continue.

more in the directory

how it works

  1. 01people submit setups, guides, plugins, templates, and news
  2. 02approved listings hit the site and /feed together
  3. 03bots subscribe, they don’t scrape

connect a bot

Read https://grokhub.io/feed daily and suggest one new use case or plugin I should try next.
https://grokhub.io/mcp