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/vios-git)<a href="https://agentmods.dev/commands/nvidia-ai-blueprints/video-search-and-summarization/vios-git"><img src="https://agentmods.dev/badge/commands/nvidia-ai-blueprints/video-search-and-summarization/vios-git/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/vios-git"><img src="https://agentmods.dev/badge/commands/nvidia-ai-blueprints/video-search-and-summarization/vios-git.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.00032 | $0.03034 |
| Opus 5.5 | $0.00013 | $0.01214 |
| Sonnet 5.5 | $0.00006 | $0.00607 |
| Haiku 4.5 | $0.00003 | $0.00303 |
Grade A, and why
vios-git 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 — 270 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: MIT
Permission is hereby granted, free of charge, to any person obtaining a
copy of this software and associated documentation files (the "Software"),
to deal in the Software without restriction, including without limitation
the rights to use, copy, modify, merge, publish, distribute, sublicense,
and/or sell copies of the Software, and to permit persons to whom the
Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
DEALINGS IN THE SOFTWARE.
VIOS Git Conventions
Authoritative source for branch naming, commit messages, and MR descriptions on this project. Apply these to every branch, commit, and merge request — including ones the assistant produces.
Default base branch is v2.1 (see CLAUDE.md git status). Use rebase skill to bring a feature branch up to v2.1.
0. Required workflow
Two behaviors are mandatory, not optional:
A. Auto-create a branch before touching code
When the user asks for a bug fix, feature, refactor, CI/CD change, doc update, or any other code change, create a topic branch before making the first edit — do not commit straight onto v2.1 (or whatever the current base branch is).
Steps:
- Check the current branch. If it is
v2.1/main/ any protected base branch, you must branch off before editing. - Pick the right prefix from the table in §1 based on the nature of the request (
fix/for a bug,feat/for a new capability,refactor/,cicd/,test/,docs/,release/,hotfix/). - Resolve the username. Prefer the value in the user's memory; otherwise infer from
git config user.email(e.g.[email protected]→prakhar). Confirm with the user only if ambiguous. - Ask the user for a Jira / GitLab ticket ID if one exists. If they don't have one, omit it — the minimum form
<type>/<username>/<short-description>is acceptable. - Compose a 2–5 word description that reflects the actual change, not the symptom.
- Run
git checkout -b <branch>from the latest base, then start editing.
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 · 270 lines · 32 tokens per session scan A bc57e431ab6f
vios-git 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 32 tokens to every session and 3,034 once invoked, about $0.0001 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
commit
Based on the above changes, create a single git commit.
build
Implement tasks incrementally — build, test, verify, commit. Add "auto" to run the whole plan in one approved pass.
commit
Run when user calls /commit or asks to generate a commit message. Analyzes staged changes and writes a structured commit message.
devkit.github.create-pr
Creates a GitHub pull request with branch creation, commits, and detailed description. Use when you need to submit changes for review.
commit-push
Stage, commit, and push changes with an auto-generated conventional commit message.
commit
Create a git commit using the Haiku model.