Borrowing it
Nothing to install: this file belongs to sylphiette269/premiere-mcp-editor-cn. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/sylphiette269/premiere-mcp-editor-cn/main/.codex/skills/premiere-bridge-verification/SKILL.mdgit clone --depth 1 https://github.com/sylphiette269/premiere-mcp-editor-cnWrote 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/sylphiette269/premiere-mcp-editor-cn/premiere-bridge-verification)<a href="https://agentmods.dev/skills/sylphiette269/premiere-mcp-editor-cn/premiere-bridge-verification"><img src="https://agentmods.dev/badge/skills/sylphiette269/premiere-mcp-editor-cn/premiere-bridge-verification/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/sylphiette269/premiere-mcp-editor-cn/premiere-bridge-verification"><img src="https://agentmods.dev/badge/skills/sylphiette269/premiere-mcp-editor-cn/premiere-bridge-verification.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.00028 | $0.00324 |
| Opus 5.5 | $0.00011 | $0.00130 |
| Sonnet 5.5 | $0.00006 | $0.00065 |
| Haiku 4.5 | $0.00003 | $0.00032 |
Grade A, and why
premiere-bridge-verification 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.
What it actually says
Premiere Bridge Verification
Overview
This skill keeps the MCP side and CEP side pointed at the same bridge and verifies the command protocol still matches runtime expectations.
When to Use
- Editing
cep-panel/js/bridge-config.js - Editing
src/bridge/index.tsorcep-panel/js/panel.js - Changing
command-*.json/response-*.jsonbehavior - Debugging timeout, expiry, or recovery script issues
Verification Loop
- Confirm the effective bridge directory.
- Preferred:
PREMIERE_TEMP_DIR - Fallback:
dirname(PREMIERE_MCP_COMMAND_FILE) - CEP side:
bridge-config.js
- Preferred:
- Confirm the command shape.
- legacy action envelope
- raw script envelope with
script,timeoutMs,expiresAt
- Run targeted tests for panel and server surface.
- Run full
npm testandnpm run build.
Quick Checks
bridge-status.jsonshould advertiseper-requestorlegacyexplicitly.- CEP should reject expired raw script commands with
command_expired. - Node and CEP must read and write the same directory.
Common Mistakes
- Changing only the Node env or only the CEP config
- Verifying legacy mode but not per-request mode
- Treating a timeout as a tool bug before checking bridge directory mismatch
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 · 42 lines · 28 tokens per session scan A 8d1e63824594
premiere-bridge-verification is a skill published in the GitHub repository sylphiette269/premiere-mcp-editor-cn (8 stars, last pushed 7mo ago), licensed MIT. It adds 28 tokens to every session and 324 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-08-31.
Other skills, from other repositories
arxiv-agentic-verifier
Source Paper: Scaling Agentic Verifier for Competitive Coding (ID: 4a4c4dae6a5145ebc4d62eb2d64b0f0f) Type: Code Verification / Test Generation.
empirical-verification
Scientific method for software. Use when debugging, reviewing surprising behavior, or before claiming code works -- always tether assumptions to reality with a small experiment.
blazemeter-troubleshooting
Comprehensive troubleshooting guide for BlazeMeter, covering API Monitoring, Performance Testing, general issues, integrations, and security. Use when troubleshooting for (1) API Monitoring issues (Radar Agent auth, SSL certificates, debug tests), (2) Performance Testing issues (high response time, 500 errors, partial…
closed-loop-development
Use when building, debugging, or verifying software inside an Agent Machine. Teaches the agent to write code, run the service, hit endpoints, inspect logs, drive the browser, and iterate without asking the user to be the test harness.
qa
Systematically QA test a web application and fix bugs found. Runs QA testing, then iteratively fixes bugs in source code, committing each fix atomically and re-verifying. Use when asked to "qa", "QA", "test this site", "find bugs", "test and fix", or "fix what's broken". Proactively suggest when the user says a…
windows-test-truth
Diagnose Windows test runs that lie — os error 4551 means the binary never executed, and a workspace test total can silently lose every suite after a blocked one. Use when cargo test reports a failure with no failing test named, when a test count looks lower than expected on Windows, or when a freshly built binary…