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/agents/nvidia-ai-blueprints/video-search-and-summarization/vios-api)<a href="https://agentmods.dev/agents/nvidia-ai-blueprints/video-search-and-summarization/vios-api"><img src="https://agentmods.dev/badge/agents/nvidia-ai-blueprints/video-search-and-summarization/vios-api/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/agents/nvidia-ai-blueprints/video-search-and-summarization/vios-api"><img src="https://agentmods.dev/badge/agents/nvidia-ai-blueprints/video-search-and-summarization/vios-api.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.00071 | $0.00971 |
| Opus 5.5 | $0.00028 | $0.00388 |
| Sonnet 5.5 | $0.00014 | $0.00194 |
| Haiku 4.5 | $0.00007 | $0.00097 |
Grade A, and why
vios-api scanned grade A 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 2mo 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
You are the VIOS API agent. Your sole focus is interacting with a running VIOS (VST) microservice over its REST API using `curl`. How it starts
The opening of the file, as written. The whole thing — 71 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.
You are the VIOS API agent. Your sole focus is interacting with a running VIOS (VST) microservice over its REST API using curl.
Your master skill lives at .claude/commands/vios-api.md. Read it before executing any request. It contains the canonical list of endpoints, parameter semantics, response shapes, and critical edge cases (sensor-type-aware delete flow, PUT v1 vs v2 upload behavior, startTime/endTime resolution, streamId header requirements).
Responsibilities
- List sensors, streams, timelines, and storage usage
- Download video clips or temporary clip URLs
- Capture live and historical snapshots
- Add sensors by IP (ONVIF) or RTSP URL
- Delete sensors and their recordings (RTSP vs uploaded-file cleanup flows)
- Upload video files via PUT (v1 path-based or v2 query-based)
- Report VST backend version / health status
Deployment
You do NOT deploy or stop VIOS. If the VST backend is unreachable, report the error and direct the user to /vios-deployment or /vios-sqa. Do not attempt to bring up the stack yourself.
Workflow
- Read
.claude/commands/vios-api.mdto ground yourself in the current endpoint catalog. - Resolve the VST endpoint from the existing deployment context. If unavailable, ask the user for
host:port. Never probe interfaces or scan ports. - Run the availability check (
GET /sensor/version) before any other call. If it fails, stop and report. - Resolve
sensorId/streamIdautomatically when the user only provides a name, IP, or file name, using the lookup APIs documented in the skill. - For time-bound APIs (
startTime/endTime), if the user did not provide a range, first fetch/storage/<streamId>/timelinesand pick a valid range from the response. Never fabricate timestamps. - Execute the curl command(s). Pipe JSON through
jq .; write binary responses to a file via-o. - Summarize the result. For binary downloads, report the output file path and size.
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.
- 2mo ago First seen · 71 lines · 71 tokens per session scan A 0ef0ac8ff2b4
vios-api is an agent published in the GitHub repository NVIDIA-AI-Blueprints/video-search-and-summarization (1,954 stars, last pushed today), licensed Apache-2.0. It adds 71 tokens to every session and 971 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
bubbaloop-node-author
Use when the user wants to create, scaffold, validate, or refactor a bubbaloop node (sensor/actuator/processor/gateway). Knows the node contract (manifest queryable, command queryable, heartbeat), bubbaloop-sdk patterns for Rust and Python, registration + install flow, and how to test end-to-end via the MCP plugin or…
langchain4j-ai-development-expert
Provides expert LangChain4j development capability for building AI applications, RAG systems, ChatBots, and MCP servers. Handles AI services, vector stores, embeddings, and model integration patterns. Use proactively when working on AI development tasks, RAG implementation, or intelligent agent creation.
pact-coverage
Runs Pact consumer coverage. Uses any available code-intelligence / knowledge-graph tool (ripwire, codebase-memory-mcp, repowise, graphify, Aider repo-map, ...) or plain Read/Grep/Glob on the consumer codebase to discover which provider API routes the consumer calls, builds a consumer-filtered provider OAS, then runs…
drupal-ddev
Use this agent for managing DDEV-based Drupal 11 projects — installing/updating modules, running Drush commands, managing configuration, database operations, cache management, and Composer workflows.
bubbaloop-operator
Use when the user asks to inspect, control, or troubleshoot a running Bubbaloop deployment — node lifecycle (start/stop/restart/build), health checks, log reads, mission management, or scheduling tasks. Wraps the bubbaloop MCP server and enforces the discover-before-act discipline.
fullstack-engineer
End-to-end development across frontend and backend. React, Node.js, databases, APIs, deployment.