/brag Free Claude Code + more

Your project, as a launch video. One command.

Your agent reads what you built and renders a 20-second video with music, motion and a caption to post. No editor needed.

Get the free setup guide

By Raj Singh · October 2026 · 6 min read

FREE SETUP GUIDE

Get your first video right.

  • The install for Claude Code, Codex or Cursor
  • What to install first so the render works
  • The flag that makes it vertical for Instagram
  • The one file to check before it renders
  • How to keep private data off screen

One email opens every guide in the library.

One email. No follow-up unless I ship something that fits.

WHAT YOU NEED
  • An agent that supports skills: Claude Code, Codex CLI, opencode, Cursor, Gemini CLI, Antigravity
  • Node.js 22 or newer, and FFmpeg on your PATH
  • The Hyperframes CLI for the full `/brag`, run through npx. Check it with npx hyperframes doctor before your first run. /brag-slim doesn't need it
  • A project with a visible interface, or a live website URL. It needs something to point at
  • No setup at all? Paste your site's link at letsbrag.app, the project's hosted version, and it sends back the video
INSTALL

One command, whichever agent you use

On Claude Code the marketplace install is the tidiest, and it brings the lean variant with it. Everywhere else the skills CLI does it in one line. Add -g to install globally, or drop it to scope the skill to the project you are in.

Claude Code

claude codethe plugin route
/plugin marketplace add latent-spaces/brag /plugin install brag@brag

Any other agent

terminalCursor, Codex, opencode, Gemini CLI
$ npx skills add https://github.com/latent-spaces/brag --skill brag -g → or --skill brag-slim for the variant with no video service

Then open a project and say let's /brag about this. It reads the code, writes a plan, composes the video and renders it. Expect to sit through a few minutes of work, not a few seconds.

Prove itRun it on a small project with a real interface, then open brag-output/brag-plan.md before you look at the video. If the plan names a specific thing your project does, the render will be good. If it reads like it could be about any project, stop there and give it a tone.
CONFIGURE

There is no config file, only flags

Nothing to set up and nothing to remember between runs. Everything is decided at the moment you invoke it, in plain words or flags, and the defaults are already the right answer for a feed.

in your agentplain words work too
› let's /brag about this › /brag --tone "fake Series A launch from 2016" › /brag --tone deadpan --format vertical --voice
OptionDefaultWhy I change it
--toneinferredThe single highest-leverage flag. Left alone it guesses from your project. Freeform direction beats the presets: describe the video you want in a sentence and it keeps your wording through the plan.
--formatwideVertical for anywhere people watch on a phone. The default is wide, which is right for a README embed or a demo on a laptop, and that is a smaller share of where these actually get seen.
--voiceoffLeave it off. Feeds autoplay muted and narration competes with your on-screen text. Turn it on for a video you will send to one person, not for a post.
--durationauto, 15 to 25sThe automatic choice is almost always right, and the skill treats the upper bound as a hard rule. Override only if you have a reason you can say out loud.
--titleinferredIt takes the name from your project, which is wrong whenever your repo name is not your product name. One flag, and the first frame stops saying my-app-v2-final.
On Opus 5.5The skill hands off to its lean variant automatically and tells you it did. That variant builds the whole video itself with the tools on your machine, with no video service and no bundled assets. Add --full to force the original path, or --voice, which the lean one does not do.
DAILY DRIVING

What lands on disk, and in what order

Four artefacts per run, in a brag-output/ folder beside your code. Read them in order, because each one is cheaper to fix than the thing after it. Stopping at the plan costs you nothing; fixing a bad render costs you the whole run.

  • The plan, first. brag-plan.md holds the angle and a beat-by-beat storyboard with timings. This is where you intervene.
  • Then the brief. composition-brief.md is what gets handed to the renderer. Worth a skim if the plan was good but the video was not.
  • Then the video. brag.mp4, with a chosen poster frame baked in as frame 0, so the thumbnail is deliberate rather than whatever frame landed first.
  • Then the caption. share-copy.txt. Edit it. It is written for a generic reader, and you know your audience.

Run it again and it writes to a timestamped folder rather than overwriting the last one, so iterating on tone is safe. Keep the run you liked and delete the rest.

WHEN IT DRIFTS

Two ways it comes out wrong

The video could be about any project
It did not find enough to look at, usually because the interface lives behind a login or the project is mostly backend. Give it a tone and point it at the part with a face, or run it after you have a landing page.
Something private appears on screen
Stop and delete the render. The skill excludes secret files by rule and substitutes stand-ins for real user data, but seed data with real names will pass that filter. Fix the fixtures, not the video, then run it again.
On WindowsThe repo publishes the skill to each agent through symlinks, which Git will not create unless core.symlinks is true and you are in Developer Mode or running as administrator. If discovery fails, copy skills/brag/ into the agent's own skills directory by hand.
THE SHAPE OF IT

Where everything lives

brag-output/brag-plan.mdthe angle and the storyboard. Read this one brag-output/brag.mp4the render, with the poster baked as frame 0 brag-output/share-copy.txtthe caption, which you should edit skills/brag/references/the tone definitions and the creative rules examples/five fake products the authors use as a benchmark

The examples folder is the fastest way to judge it before installing anything: five deliberately absurd products, each with a video, showing what the tones actually do.

That is the whole thing

One install, one sentence to invoke it, one file to read before it renders. The thing you finished goes out looking like it was worth finishing, and you never open an editor.

Open on GitHub →

↑ Unlocks the moment you submit the form above.

RS
WRITTEN BY

Raj Singh

I'm Raj Singh, founder of DebtOps.ai and a Claude certified partner. Over the last five years I've managed $25M in ads, built AI solutions for Fortune 100 companies, and installed AI operating systems and AI brains inside small businesses. Everything here is something I've shipped, debugged, or watched a client ship. My goal with AgileSingh is to make you irreplaceable in this AI age.

$25M
Ads managed · 5 yrs
F100
Enterprise AI builds
Claude
Certified partner
36
Guides shipped
More guides

Ship it, then show it.

The Claude Plugins Directory guide covers the official add-ons for Claude Code, and the OpenBB guide gives Claude live market data for free.

Keep going

Back to all systems