What is vibe-editing CLAUDE.md?

Project instructions for a video-editing workflow that turns long videos into captioned vertical clips and other branded videos. They explain how the project should be run and how finished files should be delivered.

Use them to make clips from a video or link, create horizontal highlight videos, set up the project when needed, or change its branding.

They let a coding agent handle the editing workflow for a non-technical creator without requiring terminal commands or manual file editing.

How maddexritter-rgb/vibe-editing configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to maddexritter-rgb/vibe-editing. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/maddexritter-rgb/vibe-editing/main/CLAUDE.md

Clone the repo

git clone --depth 1 https://github.com/maddexritter-rgb/vibe-editing

Made for: Claude Code.

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/instructions/maddexritter-rgb/vibe-editing/claude-md/github.svg)](https://agentmods.dev/instructions/maddexritter-rgb/vibe-editing/claude-md)

Your own site

<a href="https://agentmods.dev/instructions/maddexritter-rgb/vibe-editing/claude-md"><img src="https://agentmods.dev/badge/instructions/maddexritter-rgb/vibe-editing/claude-md/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/instructions/maddexritter-rgb/vibe-editing/claude-md"><img src="https://agentmods.dev/badge/instructions/maddexritter-rgb/vibe-editing/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 838 This file is loaded in full into every session.

When invoked 838 The same file — it is already loaded in full.

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.00838	$0.00838
Opus 5	$0.00419	$0.00419
Sonnet 5	$0.00168	$0.00168
Haiku 4.5	$0.00084	$0.00084

Measured 10d ago against content hash 918be81a6754, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

vibe-editing CLAUDE.md 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 10d 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.

CLAUDE.md · 50 lines

How it starts

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

Vibe Editing — how to run this project

This folder is Vibe Editing: a pipeline that turns a long video into finished, captioned, face-tracked vertical clips, in the creator's own brand. It's built to be run by non-technical creators — so when you help someone here, do the work yourself, never make them run terminal commands or hand-edit files, and explain what's happening in plain English.

Making clips (the main job)

When the user gives you a video — a YouTube/URL link or a local file — and asks for clips in ANY plain-English way ("make clips from this", "cut this up", "shorts from this", "/edit "):

Read plugins/vibe-editing/skills/edit/SKILL.md and follow its spine end-to-end.
Put source footage in the project's 00_SOURCE/, scratch in 10_WORK/, and finished clips in 20_DELIVER/. Show the user the delivered clips when you're done.
The pipeline mines the strongest moments, hand-cuts, face-tracks to 9:16, captions, mixes music, renders, and runs a 6-gate self-audit — a clip that fails a gate doesn't ship.

You do not need the /edit slash command or any plugin install — run the workflow directly from the scripts in plugins/vibe-editing/. (A /edit shortcut is available if the user wants it: /plugin marketplace add . then /plugin install vibe-editing@vibe-editing-marketplace.)

Horizontal "mid" videos (the highlight skill)

If the user wants HORIZONTAL 16:9 "mid" videos for SUBSCRIBER growth from a long recording — "mine highlights", "make mids", "highlights channel", "post and schedule these" — read plugins/vibe-editing/skills/highlight/SKILL.md and follow it. These are regular 16:9 videos, NOT 9:16 shorts (shorts = the edit pipeline above). The CTA outro is user-supplied and optional at brand/cta/outro.mp4. POST mode titles + schedules to the user's OWN YouTube via their own Google sign-in — never any other account.

First-time setup (only if it isn't set up yet)

If plugins/vibe-editing/.venv is missing, or python3 plugins/vibe-editing/doctor.py reports missing tools, set it up first: install only what's missing yourself (ffmpeg, yt-dlp, tesseract, rclone via Homebrew; a .venv with the kit's deps + faster-whisper). A free Groq key in plugins/vibe-editing/config/keys.env makes transcription ~10× faster; without it, it uses free offline transcription. Full first-run + brand interview: ONBOARDING.md.

Read the full file on GitHub · 50 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.

10d ago First seen · 50 lines · 838 tokens per session scan A 918be81a6754

Subscribe to this mod's changes

vibe-editing CLAUDE.md is an instructions file published in the GitHub repository maddexritter-rgb/vibe-editing (7 stars, last pushed 2mo ago), licensed MIT. It adds 838 tokens to every session, about $0.0042 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.

Creative and media

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,153 tokens

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 6,785 tokens

vibe-editing: Instructions file for Claude Code