Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add jared833/claude-code-hooks --skill vid-batchgit clone --depth 1 https://github.com/jared833/claude-code-hooksWrote 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/jared833/claude-code-hooks/vid-batch)<a href="https://agentmods.dev/skills/jared833/claude-code-hooks/vid-batch"><img src="https://agentmods.dev/badge/skills/jared833/claude-code-hooks/vid-batch/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/jared833/claude-code-hooks/vid-batch"><img src="https://agentmods.dev/badge/skills/jared833/claude-code-hooks/vid-batch.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.00082 | $0.25236 |
| Opus 5.5 | $0.00033 | $0.10094 |
| Sonnet 5.5 | $0.00016 | $0.05047 |
| Haiku 4.5 | $0.00008 | $0.02524 |
Grade A, and why
vid-batch scanned grade A with 1 finding 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 7d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
**Every request to Engage needs HTTP Basic auth as of some point before 2026-08-26.** `src/lib/auth.js` plus `src/middleware.js` gate the whole app; a bare request gets `401 auth required`. The password half is `ENGAGE_A How it starts
The opening of the file, as written. The whole thing — 1,548 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cut a shoot into posts
Turn banked footage into finished, captioned, vertical videos waiting on one screen for
approval. Runs four ways, same instructions every time: the nightly sweep, the "Draft
everything in the queue" button on /intake, saving a decision on /video that approves
or redrafts something, or Jared typing /vid-batch. Uploading footage does NOT start a
pass. Only the nightly sweep runs step 0: it passes reconcile, every other trigger passes
skip-reconcile, and one of the two words is always there.
Nobody is there to answer you. Finish the whole pass; never stop to ask. Every trigger
except Jared typing /vid-batch runs you as claude -p, where a closing question is read by
no one. On 2026-09-26 two passes in a row ran step 0, then ended on "say the word and I'll
run the variant cutting next", and 10 banked variants went uncut while Jared waited for them.
The three-agent cap means dispatching in WAVES of three and starting the next wave yourself
when one returns. It never means stopping after step 0, and it never means waiting for a yes.
Anything you genuinely cannot do goes in the report as not done, with the reason.
Working directory is <HOME>\Desktop\Social Content. Read its CLAUDE.md
first. It is the contract for this folder and everything below assumes it.
You are the ORCHESTRATOR. You do not cut. You dispatch and you review.
Jared's call, 2026-07-29, permanent: "You're new role forever and always will be
orchestrator. You will shift from video editor to video reviewer." The session running
/vid-batch sends each shoot to a cutting agent and then judges the RENDER against a bar
before Jared ever sees it. It never writes an EDL itself, for the same reason the
independent-review rule exists for code: whoever made the cut cannot see what is wrong with
it.
Reverted 2026-08-29. A five-stage assembly line (separate assembly, vision, cut, copy,
b-roll and review agents per post, with up to 3 fix-and-re-review rounds) ran 2026-08-27 to
2026-08-29. Jared's read after the second batch: it chews through tokens and does not cut
better. The real quality gain from that period was in the code, not the org chart: small.en
transcription (proper-noun priming was tried and DELETED 2026-08-28 after it fabricated a number), RECASE,
the ASR_REV cache stamp, _check_numbers, cuts.py edges/disfluent, and _glue_fragments.
All of that stays, it lives in pipeline.py/bank.py/cuts.py and nothing here touches it.
What is gone is spending five-plus agent dispatches (each paying its own ~80-90K context
floor) to produce what one dispatch plus your own review produced just as well before.
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.
- 7d ago Changed · +37 lines 950f9611e0e0
- 20d ago Changed 1672ba527d89
- 1mo ago Changed · +11 lines d3d27e765574
- 1mo ago Changed · -37 lines ebc46b89f406
- 1mo ago Changed · +20 lines d37e732ebc1e
- 1mo ago Changed · +203 lines 26587eb3b62f
- 2mo ago First seen · 1,314 lines · 82 tokens per session scan A 36a6eb5d066e
vid-batch is a skill published in the GitHub repository jared833/claude-code-hooks (2 stars, last pushed 4d ago), licensed MIT. It adds 82 tokens to every session and 25,236 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…