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 grayhatdevelopers/vidxp --skill vidxp-installgit clone --depth 1 https://github.com/grayhatdevelopers/vidxpWrote 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/grayhatdevelopers/vidxp/vidxp-install)<a href="https://agentmods.dev/skills/grayhatdevelopers/vidxp/vidxp-install"><img src="https://agentmods.dev/badge/skills/grayhatdevelopers/vidxp/vidxp-install/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/grayhatdevelopers/vidxp/vidxp-install"><img src="https://agentmods.dev/badge/skills/grayhatdevelopers/vidxp/vidxp-install.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00078 | $0.01166 |
| Opus 5.5 | $0.00031 | $0.00466 |
| Sonnet 5.5 | $0.00016 | $0.00233 |
| Haiku 4.5 | $0.00008 | $0.00117 |
Grade A, and why
vidxp-install 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.
How it starts
The opening of the file, as written. The whole thing — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Install VidXP
Reuse a working local VidXP setup when the user approves it. Otherwise, help them choose a setup, install only what they approve, verify it, and connect Codex to its local MCP server.
Check for an existing installation first
Before offering a new install, look for every vidxp executable available to the local shell. Do not modify any candidate. For each one, run:
<absolute-vidxp-path> --version
<absolute-vidxp-path> desktop-probe --json --desktop-version codex-plugin --request-id codex-install
For each successful probe, show the user its executable, version, data_root, repository_root, and model_root. These are the installation's effective paths; existing downloaded models under the reported model_root can be reused. Ask the user to confirm whether to reuse that installation and those paths.
If the user approves reuse, skip installation and upgrades. Use executables from that same environment, preserve the reported paths when registering MCP, and repair a missing surface or dependency only with approval. If no compatible installation is found or the user declines reuse, continue with the setup choice.
Start with the choice
Determine which surface the user wants before downloading anything:
- Recommend Desktop when they want a guided installer, managed runtime, feature selection, or browser interface.
- Recommend CLI when they want scripting, terminal control, automation, or a minimal agent-only setup.
- Clarify that both keep video processing local. The plugin itself is only the bootstrap and agent guidance; VidXP provides the actual MCP server after installation.
- A browser-only ChatGPT session cannot install native software. Continue only when the agent has an authorized local shell, or give the user the exact manual steps.
Ask before starting an installer, changing a tool environment, or downloading models. Do not download model weights until the user has chosen the search capabilities that need them.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 89 lines · 78 tokens per session scan A ee855a2ce116
vidxp-install is a skill published in the GitHub repository grayhatdevelopers/vidxp (59 stars, last pushed yesterday), licensed MIT. It adds 78 tokens to every session and 1,166 once invoked, about $0.0003 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-30.
Other skills, from other repositories
native-subtitle-quote-image
A tool for turning selected video moments and their subtitles into tall social-media images. It supports either keeping subtitles already embedded in the video or drawing approved text onto real video frames.
evidence-video
Create the house-style LeClap before/after PR or MR evidence video with build.py and its JSON template. Use when preparing this specific artifact, capturing its evidence, or debugging its render.
authoring-video-templates
Use when creating or editing a video template JSON (the template descriptor), adding or changing sections/filters/maps/variables/transitions/looks/motion/audio/layers/registered effects/creative direction, or debugging template validation errors in ffmpeg-video-composer.
pr-evidence
Use when opening or updating a pull request whose diff touches apps/leclap-web or apps/leclap-expo. Its description must carry before/after snapshots and a before/after evidence video rendered with LeClap itself. Covers what to capture, how to render the video, where the media live and how to embed them.
core-architecture-patterns
Use when adding a segment type, platform adapter, editor manager, core service, or descriptor effect (look/grade/motion/text/section-audio field), integrating a registered effect backend in packages/ffmpeg-video-composer, or when wiring new dependencies into the tsyringe container.
ondevice-ffmpeg-engine
Use when building, modifying, or consuming the on-device FFmpeg engine — the Rust crate packages/ffmpeg-engine, the leclap-ffmpeg Expo native module, the run/probe/version/cancel API, the uniffi bindings, build-engine.sh, or the FFmpeg-from-source toolchain in scripts/ffmpeg.