Amir Mushich open-sources a Codex workflow for Instagram Reels

• Amir Mushich’s Codex workflow turns project context and screencasts into a Reel, cover and caption, with feedback and approval in his walkthrough.
• The publication Skill is reusable across development chats, and the release post links the open-source starter kit.
• The public API adapter has not yet created a live post: the release README linked by the repository announcement says the first Reel used Buffer’s browser interface.

Approval sticks to the exact package: the delivery guide requires renewed review when the caption, destination, cover or URLs change. The best production detail is in the demo method: horizontal footage gets a full-width inset when a vertical crop would destroy the interaction.

Mushich’s source project was a clothing-store demo using Molimao Sarajevo products. He credited @cambreedesigns for the original interaction concept in his demo thread and described three production steps:

1. Start with real product photographs.
2. Generate a rotation for each product through the LTX API, using LTX-2.5.
3. Code the interface with Astra 6 inside Codex.

Generated product rotations inside the Molimao interface

Mushich described the Reel as agent-crafted and agent-published with “zero manual actions” in his walkthrough. His documented flow still reserves written feedback and approval for him:

1. Input: project context and an automated screencast.
2. Publication Skill: personal visual and copy rules.
3. Preparation: a vertical Reel, headline, music, intro footage, cover and caption.
4. Review: text feedback, revision and approval.
5. Publishing: delivery through Buffer to Instagram.
6. Verification and archive: check the live post; save the MP4, caption and render settings; record the post URL and publication receipt.

Mushich’s announcement described delivery through the Buffer API. The release README specifies that the demonstrated post used Buffer’s browser interface.

The released adapter has automated tests and live read-only API checks, but creating posts on live social accounts remains untested. Full cold-start runs across Codex, Claude Code and Hermes are also untested in this release.

The MIT-licensed repository documents installation for Codex, Claude Code and Hermes. Its bootstrap prompt checks actual tool access, asks for missing inputs and learns from a bounded sample of the creator’s content, without assuming access to every account or chat.

The reusable parts cover:

• Personal profile: voice, visual preferences and asset locations.
• Portable Skill: the publication process for later development chats.
• Channel variants: separate packages with destination-specific format, copy, framing and timing.
• Buffer CLI: channel inspection, planning, submission and delivery tracking.

Rendering uses tools available in the agent’s environment. The repository excludes a universal video editor, media hosting and Mushich’s private production assets.

His small media engine currently targets 9:16, he said in a reply, with additional formats planned.

Mushich’s production method defines eight rules for the agent:

1. Real behavior: preserve the working interaction, essential UI and cursor context; distinguish concept studies from client work.
2. Visible proof: choose the demonstrated behavior before writing its headline and caption.
3. Destination framing: preserve interaction context when reframing horizontal footage; avoid accelerating deliberately timed UI.
4. Explanation: use a concise headline, with technical details and credits in the caption where appropriate.
5. Personal style: derive typography, alignment, spacing and motion from the creator’s examples. Mushich’s optional Reel layout uses one centered headline block without explanatory microcopy.
6. Actual assets: record transition settings and the chosen music segment’s offset, gain and fades; balance music separately from sound effects.
7. Rendered-output checks: inspect legibility, framing, seams, timing, audio peaks and the beginning and end.
8. Precise provenance: distinguish the coding agent, media model and original concept author; avoid invented engagement improvements or time savings.

Buffer’s media-hosting documentation requires publicly accessible media URLs rather than local file uploads. Those URLs must remain reachable until publication, including queued posts.

The repository’s delivery lifecycle adds safeguards around the approved export:

• Package hash: approval binds to the complete package. Changes to local media also block delivery.
• Media integrity: the CLI downloads each hosted asset and checks its bytes against the reviewed local export. Buffer can still encounter separate hosting restrictions.
• Interrupted submissions: a submission-uncertain receipt is written before creating the post. A lost response blocks automatic recreation while the existing attempt is investigated.
• Publication evidence: Buffer’s reported status and external link are stored separately from an independent check of the destination’s live post.

The adapter requires Node.js 22+ and no npm dependencies. External writes require --commit; submit otherwise defaults to a dry run.