jev-surfaces

jev-surfaces is a cursor rule for Cursor from leancoderkavy/premiere-pro-mcp. It costs 16 tokens per session (167 once invoked), scanned A, original, MIT.

A set of rules for choosing which parts of a codebase to inspect first. It separates source files, plugins, workflows, documentation, and published claims into defined areas.

In plain words
What is it for?
Use it when investigating the structure or capabilities of a Premiere Pro integration, its MCP tools, its plugins, its documentation, or its release claims.
Why use it?
It reduces unfocused file reading and helps an agent check the most relevant code before making judgments about a project.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit Use it when investigating the structure or capabilities of a Premiere Pro integration, its MCP tools, its plugins, its documentation, or its release claims.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/leancoderkavy/premiere-pro-mcp/jev-surfaces
Install

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.

Clone the repo
git clone --depth 1 https://github.com/leancoderkavy/premiere-pro-mcp

Made for: Cursor.

Wrote 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.

agentmods badge for jev-surfaces

README.md
[![agentmods](https://agentmods.dev/badge/rules/leancoderkavy/premiere-pro-mcp/jev-surfaces/github.svg)](https://agentmods.dev/rules/leancoderkavy/premiere-pro-mcp/jev-surfaces)
Your own site
<a href="https://agentmods.dev/rules/leancoderkavy/premiere-pro-mcp/jev-surfaces"><img src="https://agentmods.dev/badge/rules/leancoderkavy/premiere-pro-mcp/jev-surfaces/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.

agentmods 80×15 button for jev-surfaces

Your own site · 80×15
<a href="https://agentmods.dev/rules/leancoderkavy/premiere-pro-mcp/jev-surfaces"><img src="https://agentmods.dev/badge/rules/leancoderkavy/premiere-pro-mcp/jev-surfaces.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 16 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 167 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00016 $0.00167
Opus 5.5 $0.00006 $0.00067
Sonnet 5.5 $0.00003 $0.00033
Haiku 4.5 $0.00002 $0.00017

Measured 16d ago against content hash 8fc0c1a8da12, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

jev-surfaces 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 16d 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.

.cursor/rules/jev-surfaces.mdc · 15 lines

What it actually says

Context surfaces

When scoring file candidates, use these exclusive surfaces:

  • src/tools, src/server.ts, src/workflows — MCP tools, schemas, client instructions
  • src/bridge, cep-plugin — production CEP / ExtendScript
  • uxp-plugin, src/tools/uxp* — preview UXP only; no silent CEP fallback
  • docs/claims-registry.*, README.md — public claims (the website lives in leancoderkavy/premiere-pro-mcp-site)
  • plugins/**/SKILL.md, claude-plugins/**/SKILL.md — keep both copies identical
Changes

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.

  1. 16d ago Changed · -1 lines 8fc0c1a8da12
  2. 24d ago First seen · 16 lines · 16 tokens per session scan A 2489fc5e2b88

Subscribe to this mod's changes

jev-surfaces is a cursor rule published in the GitHub repository leancoderkavy/premiere-pro-mcp (387 stars, last pushed today), licensed MIT. It adds 16 tokens to every session and 167 once invoked, about $0.0001 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-22.