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/ui-test)<a href="https://agentmods.dev/commands/nvidia-ai-blueprints/video-search-and-summarization/ui-test"><img src="https://agentmods.dev/badge/commands/nvidia-ai-blueprints/video-search-and-summarization/ui-test/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/ui-test"><img src="https://agentmods.dev/badge/commands/nvidia-ai-blueprints/video-search-and-summarization/ui-test.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.00012 | $0.01242 |
| Opus 5.5 | $0.00005 | $0.00497 |
| Sonnet 5.5 | $0.00002 | $0.00248 |
| Haiku 4.5 | $0.00001 | $0.00124 |
Grade A, and why
ui-test 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved.
SPDX-License-Identifier: Apache-2.0
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
Ask the user for the full VIOS UI base URL including any path prefix (e.g. http://${HOST}:${PORT}/${PATH}) if not already provided. Store it as BASE_URL for use in all navigation steps below.
Then run the following test scenarios in order. Report pass/fail for each.
Scenario 1: Live Stream
- Navigate to
BASE_URL/#/live-streams - Open the "Select Sensors" dropdown
- Pick any 2 sensors from the list (use the first two available)
- Wait for stream cards to appear (up to 10 seconds) before checking console logs
- For each selected sensor, verify:
- A stream card appears with the sensor name
- Console logs show
Stream status update received: PLAYING - Console logs show
on First FrameReceivedor FPS logs (e.g.<sensor> fps: N) - No WebRTC connection errors in console
- Take a screenshot as evidence
Pass criteria: Both sensors show PLAYING status and FPS > 0
Fail criteria: No sensors listed in dropdown, any sensor fails to reach PLAYING state, shows WebRTC connection errors, or video element never receives frames. Note: WebRTC Issue detected: {type: cpu} is a quality/degradation warning, not a connection failure — do not treat it as a FAIL.
Scenario 2: Recorded / Replay Stream
- Navigate to
BASE_URL/#/recorded-streams - Open the "Select Sensors" dropdown
- If the dropdown is empty (no sensors listed) — mark as FAIL immediately, do not proceed
- Pick any 2 sensors from the list (use the first two available)
- Wait up to 10 seconds for stream cards and recording timelines to appear
- For each selected sensor, verify:
- A stream card appears with the sensor name
- A recording timeline is visible (seek bar or timeline segment)
- Console logs show
Stream status update received: PLAYING - Console logs show
on First FrameReceivedor FPS logs (e.g.<sensor> fps: N) - No WebRTC connection errors in console
- Take a screenshot as evidence
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 · 111 lines · 12 tokens per session scan A 930001c43cda
ui-test 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 12 tokens to every session and 1,242 once invoked, about $0.0000 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 commands, from other repositories
devkit.java.write-integration-tests
Generates comprehensive integration tests for Spring Boot classes using Testcontainers (PostgreSQL, Redis, MongoDB) with @ServiceConnection pattern. Use when writing integration tests for service or repository classes.
record-test
Record user interactions to generate an end-to-end test file.
run-e2e
Run end-to-end tests against the application using Playwright or Cypress.
run-load-test
Run load and stress tests against API endpoints or web pages.
test
Write tests before implementation using Red-Green-Refactor.
ios-test
Bu komut iOS/SwiftUI uygulamasini derleyip simulator'da acarak computer use ile gorsel test yapar.