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.
/plugin marketplace add vidhook/vidhook-mcpnpx agentmods add plugins/vidhook/vidhook-mcp/vidhook-mcpgit clone --depth 1 https://github.com/vidhook/vidhook-mcpGrade A, and why
vidhook 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 yesterday.
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
{
"name": "vidhook",
"description": "Render videos from JSON via the vidhook API. Bundles the vidhook MCP server (validate / render / get_status / get_usage) and the vidhook-movie skill for authoring correct Movie JSON.",
"homepage": "https://github.com/vidhook/vidhook-mcp#readme",
"repository": "https://github.com/vidhook/vidhook-mcp",
"license": "MIT",
"author": {
"name": "vidhook"
},
"keywords": ["vidhook", "video", "video-generation", "mcp", "render"],
"userConfig": {
"api_key": {
"type": "string",
"title": "vidhook API key",
"description": "Your vidhook API key. Use a vh_test_ key for free, watermarked drafts; vh_live_ for clean, billed output. Get one at https://vidhook.app",
"sensitive": true,
"required": true
}
},
"mcpServers": {
"vidhook": {
"command": "npx",
"args": ["-y", "vidhook-mcp"],
"env": {
"VIDHOOK_API_KEY": "${user_config.api_key}"
}
}
}
}
What ships with it
1 file beside plugin.json 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.
- yesterday First seen · 30 lines scan A e478c808afa1
vidhook is a plugin published in the GitHub repository vidhook/vidhook-mcp (0 stars, last pushed 1mo 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-31.
Other plugins, from other repositories
pexo
Plugin marketplace listing 1 plugin: pexo.
sonilo-skills
Sonilo — Agent Skills for licensed music, sound-effects, dubbing, and audio-ducking generation, scored to your video's pacing and emotion.
tdmcp
Plugin marketplace listing 1 plugin: tdmcp.
bevy-skills
AI agent skills for Bevy 0.19: ECS, rendering, physics, input, assets, audio, accessibility, persistence, testing, profiling, voxels, and migration.
motion-design-skills
Motion design fundamentals, engines, and brand elements as installable skills for AI coding agents — timing, typography, color, composition, After Effects, Remotion, logos, and backgrounds.
shotcut-mcp
Full transactional editor for Shotcut projects through a local MCP server.