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/rules/nvidia-ai-blueprints/video-search-and-summarization/vios-code-review)<a href="https://agentmods.dev/rules/nvidia-ai-blueprints/video-search-and-summarization/vios-code-review"><img src="https://agentmods.dev/badge/rules/nvidia-ai-blueprints/video-search-and-summarization/vios-code-review/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/rules/nvidia-ai-blueprints/video-search-and-summarization/vios-code-review"><img src="https://agentmods.dev/badge/rules/nvidia-ai-blueprints/video-search-and-summarization/vios-code-review.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.00456 | $0.00456 |
| Opus 5.5 | $0.00182 | $0.00182 |
| Sonnet 5.5 | $0.00091 | $0.00091 |
| Haiku 4.5 | $0.00046 | $0.00046 |
Grade A, and why
vios-code-review 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 — 42 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.
Code Review
Structure feedback as: Critical (bugs, memory leaks, UB, thread-safety violations) -> Warnings (missing error handling, performance issues, style drift) -> Suggestions (optional improvements).
Focus on recently changed code unless a full audit is requested. Provide concrete examples when suggesting changes. Before proposing a fix that touches a public interface, confirm whether ABI backward compatibility must be maintained.
Clarification Protocol
Before implementing, ask if any of the following are ambiguous:
- Codec, format, or protocol context (e.g. H.264 vs H.265, RTSP vs WebRTC)
- Whether the change must maintain backward ABI compatibility
- Target platform or compiler version constraints
- Whether existing tests need updating or new ones are required
Never assume on changes that could cause ABI breakage or silent behavioral differences.
Debugging
Workflow: reproduce -> gather evidence (logs, stack traces) -> hypothesize root causes ranked by likelihood -> trace code paths through the shim layer -> isolate minimal reproduction -> fix with clear reasoning -> check for regressions.
Tools: GDB (stack traces, watchpoints), Valgrind / AddressSanitizer (memory errors), ThreadSanitizer (data races), perf / gprof (CPU profiling), GST_DEBUG + pipeline dot graphs (GStreamer).
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 · 42 lines · 456 tokens per session scan A c1c9a2f268f3
vios-code-review is a cursor rule published in the GitHub repository NVIDIA-AI-Blueprints/video-search-and-summarization (1,945 stars, last pushed today), licensed Apache-2.0. It adds 456 tokens to every session, about $0.0018 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 cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
as-contract-cast-smell
// ❌ WRONG — bypasses the family ContractSerializer seam const contract = JSON.parse(raw) as Contract; const contract = JSON.parse(raw) as Contract .