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.
/plugin marketplace add maddexritter-rgb/vibe-editing/plugin install vibe-editingWrote 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.
[](https://agentmods.dev/skills/maddexritter-rgb/vibe-editing/audit-visual)<a href="https://agentmods.dev/skills/maddexritter-rgb/vibe-editing/audit-visual"><img src="https://agentmods.dev/badge/skills/maddexritter-rgb/vibe-editing/audit-visual/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.
<a href="https://agentmods.dev/skills/maddexritter-rgb/vibe-editing/audit-visual"><img src="https://agentmods.dev/badge/skills/maddexritter-rgb/vibe-editing/audit-visual.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00096 | $0.01973 |
| Opus 5 | $0.00048 | $0.00986 |
| Sonnet 5 | $0.00019 | $0.00395 |
| Haiku 4.5 | $0.00010 | $0.00197 |
Grade A, and why
audit-visual 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 12d 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.
How it starts
The opening of the file, as written. The whole thing — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
audit-visual — visual-only quality gate
Fresh-context agent. Receives ONLY the video frames (audio stripped). Checks what a VIEWER would see, ignoring what they'd hear.
How to run
python3 ${CLAUDE_PLUGIN_ROOT}/skills/audit-visual/scripts/check.py \
--clip 20_DELIVER/v1/clip.mp4 \
--project 10_WORK/clips/<Slug> \
--out 10_WORK/audit_visual.json
ALWAYS pass --project (the clip's work dir) — it reads the real cut seams so the within-shot
pan gate fires hard. Without it, seams are self-detected (loose) and panning only warns.
Optional: --contact-sheet to generate a visual grid for manual review.
What it checks
1. CROP STABILITY — the authoritative check (background phase-correlation)
The defect a viewer sees is the CROP WINDOW jumping, not the subject moving. The
crop is rigid: if it jumps, the static background moves with it. So the gate
phase-correlates the static top band of the frame (top 22%) and reads the clip's
REAL cut boundaries from the render pipeline (10_WORK/stages/cut/<hash>.meta.json
via _shared/clip_meta.py) — same-angle jump cuts are content seams, never
"tracking failures". Without metadata, seams are self-detected from frame-diff spikes.
- Within a shot: vertical crop step ≥1.2% of height, step-confirmed (neighbors stay shifted) = FAIL. Unconfirmed transients are reported, not failed.
- Across seams: the Y-axis must hold (Y-lock / global-Y). Background dY ≥1.5% across a cut = FAIL, ≥0.9% = WARN. X may legitimately re-center. (Known-good seams measure 0.0–0.08% dY; one accepted outlier at 0.73%.)
- Zoom exemption: punch-in zooms read as band motion but are intentional — a
zoom is detected (left/right band halves move horizontally in opposite directions)
and exempted, counted in
zoom_moves_within_shots/zoom_seams. - Horizontal PAN within a shot = FAIL (2026-06-12, Guest159 regression): >8% within-shot
horizontal crop drift (when seams are known via
--project, bg static) = the frame is FOLLOWING the subject instead of holding — the "terrible keyframe" defect. Fix = reframe with--lock-x(auto-on for thepodcastpreset). Small dx for true re-centering at a content cut is exempt; in self-detected (loose) mode it warns rather than fails. - OVER-ZOOM = FAIL (2026-06-12): face AREA >20% of frame = head cropped / too tight. A chest-up
podcast/talking-head reframe sits ~8-14% (measured: known-good L3 clips 7.9-8.2%; the over-zoom
batch 20.7-23.5%). 16-20% = warn. Cause = applying source-intel's zoom (1.4-2.2) on already-chest-up
footage; fix =
--preset podcast(zoom 1.0) from the 4K master. - Moving-content footage (handheld, b-roll) is detected via baseline band motion and the stability checks are skipped with a note rather than false-failing.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 139 lines · 96 tokens per session scan A faef7c7072e3
audit-visual is a skill published in the GitHub repository maddexritter-rgb/vibe-editing (7 stars, last pushed 2mo ago), licensed MIT. It adds 96 tokens to every session and 1,973 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…