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 compimprove/adobe-premiere-mcp --skill premiere-pro-mcpgit clone --depth 1 https://github.com/compimprove/adobe-premiere-mcpWrote 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/compimprove/adobe-premiere-mcp/premiere-pro-mcp)<a href="https://agentmods.dev/skills/compimprove/adobe-premiere-mcp/premiere-pro-mcp"><img src="https://agentmods.dev/badge/skills/compimprove/adobe-premiere-mcp/premiere-pro-mcp/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/compimprove/adobe-premiere-mcp/premiere-pro-mcp"><img src="https://agentmods.dev/badge/skills/compimprove/adobe-premiere-mcp/premiere-pro-mcp.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.00064 | $0.01165 |
| Opus 5.5 | $0.00026 | $0.00466 |
| Sonnet 5.5 | $0.00013 | $0.00233 |
| Haiku 4.5 | $0.00006 | $0.00117 |
Grade A, and why
premiere-pro-mcp 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 1mo 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.
This is a copy
95% identical to premiere-pro-mcp — 7 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Adobe Premiere Pro MCP
Use this skill when working with the Adobe Premiere Pro MCP server from compimprove/adobe-premiere-mcp.
Core Rules
- Use the MCP tools for Premiere operations; do not invent ExtendScript unless the MCP tool surface is missing the needed operation.
- Prefer read-only discovery first:
get_project_info,list_sequences,list_project_items,get_active_sequence, and relevant resource reads. - Use real imported media. If the user asks to edit with assets, verify file paths exist, import them with
import_media, then place the imported project item IDs on a sequence. - Keep the temp directory consistent across the MCP server and CEP panel:
/tmp/premiere-mcp-bridgeunless the user explicitly configured another path. - Ask before destructive or externally visible actions: deleting clips/media, overwriting exports, closing projects, saving over important project files, or sending files elsewhere.
- For generated/demo edits, prefer creating a new clearly named sequence instead of modifying the user's active sequence.
- If a tool returns
success: false, report the exact error and run diagnostics before retrying blindly.
Install Workflow
If the user asks you to install or set up the MCP:
- Check the OS. The automated installer is macOS-focused.
- Clone or open the repo:
git clone https://github.com/compimprove/adobe-premiere-mcp.git
cd adobe-premiere-mcp
- On macOS, run:
npm run setup:mac
- For non-macOS or manual client setup, run:
npm install
npm run build
- Register the MCP server in the user's client with:
command: node /absolute/path/to/Adobe_Premiere_Pro_MCP/dist/index.js
env: PREMIERE_TEMP_DIR=/tmp/premiere-mcp-bridge
For Codex, prefer:
codex mcp add premiere_pro --env PREMIERE_TEMP_DIR=/tmp/premiere-mcp-bridge -- node /absolute/path/to/Adobe_Premiere_Pro_MCP/dist/index.js
Premiere Bridge Startup
After installing:
- Restart the MCP client if it reads config only at startup.
- Restart Premiere Pro.
- Open
Window > Extensions > MCP Bridge (CEP). - Set
Temp Directoryto/tmp/premiere-mcp-bridge. - Click
Save Configuration. - Click
Start Bridge. - Confirm the bridge panel says Premiere is ready before running editing tools.
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.
- 1mo ago First seen · 120 lines · 64 tokens per session scan A 6387f7f09d8b
premiere-pro-mcp is a skill published in the GitHub repository compimprove/adobe-premiere-mcp (0 stars, last pushed 2mo ago), licensed MIT. It adds 64 tokens to every session and 1,165 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 95% identical to premiere-pro-mcp, differing in 7 lines, and is treated as a copy.
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…