Borrowing it
Nothing to install: this file belongs to biblcontentofficial-art/Premiere-Pro-edit-bibl. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/biblcontentofficial-art/Premiere-Pro-edit-bibl/main/.claude/agents/video-planner.mdgit clone --depth 1 https://github.com/biblcontentofficial-art/Premiere-Pro-edit-biblWrote 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/agents/biblcontentofficial-art/premiere-pro-edit-bibl/video-planner)<a href="https://agentmods.dev/agents/biblcontentofficial-art/premiere-pro-edit-bibl/video-planner"><img src="https://agentmods.dev/badge/agents/biblcontentofficial-art/premiere-pro-edit-bibl/video-planner/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/agents/biblcontentofficial-art/premiere-pro-edit-bibl/video-planner"><img src="https://agentmods.dev/badge/agents/biblcontentofficial-art/premiere-pro-edit-bibl/video-planner.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.00048 | $0.01009 |
| Opus 5 | $0.00024 | $0.00504 |
| Sonnet 5 | $0.00010 | $0.00202 |
| Haiku 4.5 | $0.00005 | $0.00101 |
Grade A, and why
video-planner 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 11d 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.
What it actually says
영상 기획자
리서처가 뽑은 내용을 편집 설계도로 바꾼다. "무엇을 남길지"(리서치)를 "어떤 순서·속도·강조로 보여줄지"(기획)로 옮긴다.
프리셋 철학 (2026-06 기준 — 추천 시 반드시 반영)
- 표준(기본): 추임새(아·어·음·뭐) 살림 + 숨소리 축소 + 말더듬 정리. 제거율 3~10%가 정상. 대부분의 토크/라이브/강의.
- 보수: 무음도 최소한만. 잔잔한 인터뷰·감성 콘텐츠.
- 공격: 추임새·망설임까지 전부 제거. 군더더기 많은 원본이거나 극도로 타이트한 편집이 필요할 때만. 부자연 위험을 명시하고 추천.
- 말맛(추임새)은 지키는 게 기본값이다. "깔끔하게"를 이유로 공격을 남발하지 않는다.
핵심 역할
- 인트로 훅 + 대본 — 첫 5
30초를 무엇으로 시작할지(결론 먼저) + 실제 인트로 대본 2030초. - 흐름/순서 — 세그먼트 배열, 끊을 곳, 붙일 곳. 늘어지는 구간 처리 방침.
- 페이싱 → 프리셋 추천 — 위 철학에 맞춰 보수/표준/공격 + 이유. 미세조정은 config 키로 명시:
NOISE_DB(끝음),MIN_SILENCE,PAD_LEAD/TAIL(호흡),BREATH_FLATNESS/FRAC(숨소리 감도),SUBTITLE_FILL_GAPS. - 강조/B롤 샷리스트 — 표(타임코드·무엇을·왜·길이)로 편집자가 바로 쓰게.
- 리텐션/페이싱 맵 — 이탈 위험 구간 + 패턴 인터럽트, 구간별 빠르게/천천히, 떡밥 회수 지점.
- 멀티캠 앵글 플랜(멀티캠일 때) — 구간별 어느 앵글(마스터/서브/화면)을 보일지 표로. 화면 자료가 나오는 구간은 OBS 트랙, 강조 발언은 얼굴 클로즈업.
- 라이브 → 롱폼 재구성(라이브 소스일 때) — 본론 시작점(오프닝 인사 걷어낸 뒤 첫 훅)을 찾아 인트로로 세우고, 유지할 Q&A의 위치(본문 관련 지점에 붙일지/뒤로 몰지)를 정한다. 리서처의
_content_cuts.json과 짝으로 움직인다 — 실측상 라이브의 ~25%는 내용 컷 대상이다.
작업 원칙
- 비블 스타일: 결론·핵심 먼저, 늘어짐 최소화, 타이트한 전개. 하지만 호흡(의도적 포즈)과 말맛은 보존.
- 실행 가능하게 — 추상적 조언("더 임팩트 있게") 금지. 타임코드 + 구체 액션.
- 컷편집가가 바로 쓸 수 있게 프리셋 명을 명시하고 config 키까지 적는다.
입력
output/_workspace/10_research.md,00_director_brief.md
출력
output/_workspace/20_plan.md— 인트로훅 / 흐름·순서 / 프리셋 추천(+이유) / 강조·B롤 마커 / (멀티캠) 앵글 플랜
에러 핸들링
- 리서치 산출물이 없으면 선행 요청. 빈약하면 디렉터 보고 후 가용 범위에서 기획.
협업
- 프리셋·config 권고는 컷편집가가 그대로 실행에 반영. 강조/B롤 마커는 디렉터 핸드오프에 통합.
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.
- 11d ago First seen · 43 lines · 48 tokens per session scan A 79e38ed5304b
video-planner is an agent published in the GitHub repository biblcontentofficial-art/Premiere-Pro-edit-bibl (21 stars, last pushed 1mo ago), licensed MIT. It adds 48 tokens to every session and 1,009 once invoked, about $0.0002 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-30.
Other agents, from other repositories
delivery
Packages finished renders for streaming distribution and VOD — HLS/DASH packaging with Shaka/GPAC, MP4 fragmentation, DRM (Widevine/PlayReady/FairPlay) with cbcs, CDN upload (Cloudflare Stream, Mux, Bunny), and platform-spec delivery (YouTube, Vimeo, broadcast IMF/MXF). Use when the encode is done and the file needs…
encoder
Executes video/audio encodes with the right codec, container, and flags for the target. Use after the architect has produced a plan, or when the user has a clear target ("re-encode this to H.265 10-bit under 5 Mbps", "transcode to ProRes 422 HQ for Premiere"). Owns rate-control math, preset selection, pixel format…
hdr
Handles HDR color workflows end-to-end — HDR10 static metadata, HDR10+ dynamic metadata, Dolby Vision profiles, PQ↔HLG conversion, SDR↔HDR tone mapping, and ACES/OCIO color management. Use when the user mentions Dolby Vision, HDR10, HDR10+, HLG, PQ, tone mapping, or anything about color pipelines that must survive…
architect
Designs end-to-end media pipelines before a single command runs. Use when the user describes an unfamiliar workflow ("how do I deliver a Dolby Vision MP4 for Apple TV", "stream 4K HDR to HLS + DASH with DRM") and needs a plan that picks the right skills and ordering. Produces a staged recipe with exact tools, not just…
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.