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/leancoderkavy/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/rules/leancoderkavy/premiere-pro-mcp/repo)<a href="https://agentmods.dev/rules/leancoderkavy/premiere-pro-mcp/repo"><img src="https://agentmods.dev/badge/rules/leancoderkavy/premiere-pro-mcp/repo/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/rules/leancoderkavy/premiere-pro-mcp/repo"><img src="https://agentmods.dev/badge/rules/leancoderkavy/premiere-pro-mcp/repo.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.00236 | $0.00236 |
| Opus 5.5 | $0.00094 | $0.00094 |
| Sonnet 5.5 | $0.00047 | $0.00047 |
| Haiku 4.5 | $0.00024 | $0.00024 |
Grade A, and why
repo 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 26d 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
Premiere Pro MCP
Read AGENTS.md before editing. This repo is the TypeScript MCP server for Adobe Premiere Pro (premiere-pro-mcp). Production path: local stdio server plus CEP file-IPC. UXP is a capability-aware preview, not a silent CEP fallback.
- Use Node.js 24 for repo work; runtime floor is Node.js 20.19. Install with
npm ci. - Iterate with the narrowest Vitest file; finish with
npm run check. Coverage-sensitive changes also neednpm run test:coverage. - Keep diffs focused. Do not rewrite unrelated files, lockfiles, or generated inventories unless the task requires it.
- Automated tests are package evidence only. Do not claim live Premiere, npm publish, Marketplace, or deploy success without that layer's proof.
- Telemetry stays operational metadata. Never collect prompts, arguments, results, tokens, IPs, paths, or media/project names.
- Do not commit secrets,
dist/, coverage, Premiere project/media files, or.worktrees/.
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.
- 26d ago First seen · 16 lines · 236 tokens per session scan A 0b07e1f8fbfa
repo is a cursor rule published in the GitHub repository leancoderkavy/premiere-pro-mcp (387 stars, last pushed today), licensed MIT. It adds 236 tokens to every session, about $0.0009 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-09-20.
Other cursor rules, from other repositories
release-ts-sdk
Release @aptos-labs/ts-sdk or @aptos-labs/confidential-asset — version bump, changelog stamp, release PR, then tag + GitHub Release that triggers NPM publish.
npm-publish-agent
NPM Package Publishing Guidelines.
vue-typescript-patterns
A set of coding rules for Vue 3 projects using TypeScript, a language that adds type checking to JavaScript. It covers component structure, file locations, TypeScript usage, and Pinia, a library for shared application state.
nextjs-typescript-app-cursorrules-prompt-file
Cursor rules for Next.js development with TypeScript integration.
typescript-security
// NEVER: Hardcoded secrets const apiKey = "sk-proj-xxxxx".
ts
A set of TypeScript coding rules covering types, naming, file organization, error handling, and strict type checking. TypeScript is JavaScript with checks that help catch many mistakes before the program runs.