NVIDIA AI Blueprint for Video Search and Summarization (VSS) is a reference architecture for applications that use AI to search, analyze, question, and summarize live or recorded video. It is intended for building video analytics agents with vision-language models, language models, retrieval-augmented generation, and NVIDIA NIM microservices. The catalogue entries provide coding-agent rules, skills, commands, agents, instructions, and settings associated with the project.
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/NVIDIA-AI-Blueprints/video-search-and-summarizationWrote 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/commands/nvidia-ai-blueprints/video-search-and-summarization/update-vst-ui)<a href="https://agentmods.dev/commands/nvidia-ai-blueprints/video-search-and-summarization/update-vst-ui"><img src="https://agentmods.dev/badge/commands/nvidia-ai-blueprints/video-search-and-summarization/update-vst-ui/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/commands/nvidia-ai-blueprints/video-search-and-summarization/update-vst-ui"><img src="https://agentmods.dev/badge/commands/nvidia-ai-blueprints/video-search-and-summarization/update-vst-ui.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.00041 | $0.01264 |
| Opus 5.5 | $0.00016 | $0.00506 |
| Sonnet 5.5 | $0.00008 | $0.00253 |
| Haiku 4.5 | $0.00004 | $0.00126 |
Grade C, and why
update-vst-ui scanned grade C with 1 finding 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
allowed-tools: AskUserQuestion, Read, Bash(cd * && npm run install:link), Bash(cd * && npm run build), Bash(ls *), Bash(rm -rf *), Bash(cp -r *), Bash(git -C * log *), Bash(git -C * add *), Bash(git -C * status), Bash(gi How it starts
The opening of the file, as written. The whole thing — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task
Build the VST UI and deploy the compiled static assets into the vios component (services/vios) of the video-search-and-summarization repository, replacing the old files in both deployment locations, then commit the repo.
The UI source lives at <VIOS_DIR>/ui/vios-ui/ (package vst-ui-ts). The WebRTC streaming library is the sibling <VIOS_DIR>/ui/streaming-lib/ directory, built and linked by npm run install:link.
Arguments provided: $ARGUMENTS
Step 1 — Locate the vios tree
The VST UI source and its deployment targets all live inside the vios component (services/vios/) of the video-search-and-summarization monorepo. This skill runs from a session opened in that monorepo, so the tree is already checked out — no cloning is needed. Resolve VIOS_DIR (the path to the services/vios directory):
- Argument provided — if
$ARGUMENTSis non-empty, use that path directly (it should point at theservices/viosdirectory). - Current directory is the vios tree — if it contains
webrootanddeployment/scaling/ingress, use.. - Monorepo root — if
./services/viosexists, use it.
Verify the resolved directory contains ui/vios-ui and deployment/scaling/ingress. If none of the above resolves (you are not inside a checkout), ask the user for the path to their services/vios directory rather than cloning.
Store the resolved path as VIOS_DIR for subsequent steps.
The two deployment targets inside VIOS_DIR are:
TARGET_INGRESS = $VIOS_DIR/deployment/scaling/ingress/vst-uiTARGET_WEBROOT = $VIOS_DIR/webroot
The UI source directory is UI_DIR = $VIOS_DIR/ui/vios-ui.
Step 2 — Remove old VST UI assets from both targets
Remove only the VST UI files; do not touch anything else in webroot.
rm -rf $TARGET_INGRESS/assets $TARGET_INGRESS/favicon $TARGET_INGRESS/index.html
rm -rf $TARGET_WEBROOT/assets $TARGET_WEBROOT/favicon $TARGET_WEBROOT/index.html
Step 3 — Install dependencies in the VST UI repo
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 Changed · -6 lines 160e2359d8b2
- 1mo ago First seen · 150 lines · 41 tokens per session scan C 399cac1e60e2
update-vst-ui is a command published in the GitHub repository NVIDIA-AI-Blueprints/video-search-and-summarization (1,947 stars, last pushed yesterday), licensed Apache-2.0. It adds 41 tokens to every session and 1,264 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
CHANGELOG
Command "CHANGELOG" from bytedance/UI-TARS-desktop, covering 0.4.0 2024-12-10 - add logging, 1.2.29, 1.2.28, 1.2.26 and 1.2.25.
commit-push-pr
Commit, push, and open a PR.
commit
Run when user calls /commit or asks to generate a commit message. Analyzes staged changes and writes a structured commit message.
devkit.github.review-pr
Provides comprehensive GitHub pull request review with code quality, security, and best practices analysis. Use when reviewing a PR before merging.
fix-comments
Address PR review comments by implementing requested changes automatically.
review-open-prs
Command "review-open-prs" from The-Artificer-of-Ciphers-LLC/skills-from-the-artificer, covering batch pr review directive — all open prs i did not author, phase a — enumerate target prs & build the queue, phase b — per-pr directive (runs once per queued $pr), 0. context anchoring and 1. preconditions.