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.
git clone --depth 1 https://github.com/hetpatel-11/Adobe_Premiere_Pro_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/plugins/hetpatel-11/adobe_premiere_pro_mcp/premiere-pro-mcp)<a href="https://agentmods.dev/plugins/hetpatel-11/adobe_premiere_pro_mcp/premiere-pro-mcp"><img src="https://agentmods.dev/badge/plugins/hetpatel-11/adobe_premiere_pro_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/plugins/hetpatel-11/adobe_premiere_pro_mcp/premiere-pro-mcp"><img src="https://agentmods.dev/badge/plugins/hetpatel-11/adobe_premiere_pro_mcp/premiere-pro-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
Copies of this mod
1 near-identical copy found in the catalogue:
- premiere-pro-mcp — 100% identical, 0 lines differ
What it actually says
{
"$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
"name": "premiere-pro-mcp",
"displayName": "MCP Bridge for Adobe Premiere Pro",
"version": "1.1.6",
"description": "Inspect, edit, verify, and export local Adobe Premiere Pro projects through the MCP Bridge.",
"author": {
"name": "Het Patel",
"url": "https://github.com/hetpatel-11"
},
"homepage": "https://github.com/hetpatel-11/Adobe_Premiere_Pro_MCP",
"repository": "https://github.com/hetpatel-11/Adobe_Premiere_Pro_MCP",
"license": "MIT",
"keywords": ["premiere-pro", "video-editing", "mcp", "timeline", "export"],
"skills": "./skills/",
"mcpServers": "./.mcp.json"
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 26 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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 · 18 lines scan A 49a0f1797414
premiere-pro-mcp is a plugin published in the GitHub repository hetpatel-11/Adobe_Premiere_Pro_MCP (771 stars, last pushed 3d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
photoshop-mcp
Control Adobe Photoshop from Claude Code — 128 tools, recipes, generative AI.
aem-project-management
Project lifecycle management for AEM Edge Delivery Services - handover documentation, PDF generation, and project assistance.
aem-6-5-lts
All AEM 6.5 LTS skills: Workflow model design, development, triggering, launchers, debugging, and triaging; Dispatcher config authoring, advisory, incident response, performance tuning, and security hardening; Replication agent configuration, content activation, API usage, and troubleshooting for AEM 6.5 LTS and AMS…
aem-eds-content-ops
Content operations skills for AEM Edge Delivery Services: page auditing, SEO optimization, AI search (GEO), WCAG accessibility, bulk metadata, structured data, sitemap validation, and content diffing. Complements the EDS development skills with operational tooling for content teams.
adobe-for-creativity
Brings together Adobe Creative Cloud tools for images, vectors, design, and video. Edit multiple assets at once, adapt for different platforms, and complete multi-step creative workflows for polished results.
web
Browser automation and web page analysis skills: probe CDN bot protection, dismiss overlays, capture spatial DOM trees, reduce pages to skeletons, extract page resources, and detect page languages via the web CLI (plugins/web/cli; web doc extending shows how to add your own commands); drive Chrome and test extensio.