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 alivirgo/Major-AI-Skills --skill adobe-premiere-progit clone --depth 1 https://github.com/alivirgo/Major-AI-SkillsWrote 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/alivirgo/major-ai-skills/adobe-premiere-pro)<a href="https://agentmods.dev/skills/alivirgo/major-ai-skills/adobe-premiere-pro"><img src="https://agentmods.dev/badge/skills/alivirgo/major-ai-skills/adobe-premiere-pro/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/alivirgo/major-ai-skills/adobe-premiere-pro"><img src="https://agentmods.dev/badge/skills/alivirgo/major-ai-skills/adobe-premiere-pro.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.00042 | $0.02233 |
| Opus 5.5 | $0.00017 | $0.00893 |
| Sonnet 5.5 | $0.00008 | $0.00447 |
| Haiku 4.5 | $0.00004 | $0.00223 |
Grade A, and why
adobe-premiere-pro 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 6d 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 — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Adobe Premiere Pro NLE Automation AI Skill Guide (Claude)
Overview & Engine Architecture
Premiere Pro is a track-based NLE: Project → Bins → Sequences → TrackItems, with Lumetri, captions, graphics, and audio mixers. Modern automation prefers UXP (require('premierepro')) — async DOM, project.lockedAccess + executeTransaction for mutations (enforced harder since 26.3). Legacy ExtendScript (JSX) remains common for studio scripts. Delivery usually goes through Adobe Media Encoder (AME) presets (.epr). Interchange: FCPXML, AAF, EDL, CME.
Pin the studio’s major version (e.g. 25.x / 26.x): marker APIs landed ~25.6; EncoderManager helpers and stricter action locks landed in 26.3.
┌─────────────────────────────────────────────────────────────┐
│ Premiere Pro build → deliver loop │
│ │
│ Editorial model │
│ ├── Project / Productions (shared media root) │
│ ├── Sequence (timebase, frame size, sample rate) │
│ └── TrackItem / Marker / Transition / Effect │
│ │
│ Automation │
│ ├── UXP: Project.getActiveProject → lockedAccess/Actions │
│ ├── ExtendScript: app.project.activeSequence (legacy) │
│ └── Interchange: FCPXML / AAF / EDL │
│ │
│ Delivery │
│ ├── EncoderManager / AME queue + .epr presets │
│ └── Match Source vs platform H.264/ProRes/DNx masters │
└─────────────────────────────────────────────────────────────┘
When to use / when not to
Use when
- Scaffolding sequences, chapter/comment markers, bin hygiene, or AME export handoff.
- Generating or validating FCPXML/AAF/EDL for finishing round-trips.
- Relinking media under Productions / shared storage with path conventions.
What ships with it
2 files 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.
- 6d ago Changed · +77 lines · +13 tokens per session 1851fd6d2fb6
- 1mo ago Changed · -8 tokens per session 1c36269a8263
- 2mo ago First seen · 121 lines · 37 tokens per session scan A 900208ab50fe
adobe-premiere-pro is a skill published in the GitHub repository alivirgo/Major-AI-Skills (2 stars, last pushed today), licensed MIT. It adds 42 tokens to every session and 2,233 once invoked, about $0.0002 per session on Opus 5.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
edit-premiere-project
Inspect, edit, verify, save, and export an open Adobe Premiere Pro project through the premiere-pro MCP server. Use for rough cuts, timeline assembly or cleanup, clip and track changes, transitions and effects, dialogue or audio adjustments, captions, clip metadata and XMP, project organization, frame inspection, and…
develop-premiere-pro-mcp
Develop, debug, test, review, document, and release the premiere-pro-mcp repository. Use when changing MCP tools, schemas, server registration, CEP or UXP bridges, generated ExtendScript, authority profiles, packaging, release metadata, or compatibility claims in this repo.
wedding-cinematic-reel
Color-match event footage to a hero/reference clip, sync highlight cuts to music beats, and build a four-minute wedding reel.
brand-assets-setup
Generate and deploy a complete brand asset pack for a Next.js App Router project. Scans the project, prints what to generate with exact specs, then imports and wires everything correctly.
browser-audit
Run a pre-deploy browser audit of a live, preview, or local web page for accessibility, SEO, Lighthouse quality, and critical UX issues. Use when asked to audit a page/site before deployment, check WCAG 2.2 AA, WAI-ARIA, Lighthouse, accessibility, SEO, contrast, keyboard navigation, focus states, semantic HTML, forms…
workflow-node-setup
Configure, adjust, debug, and verify React Flow workflow nodes. Use when working on custom node components, especially for node handles, multi-channel connections, edge ids/styles, NodeResizer behavior, drag handles, nodrag/nowheel areas, and markdown scroll containers.