What is vios-testing-cicd?

Rules for testing VIOS and for CI/CD, the automated systems that build, check, and deliver code after changes.

Use them when writing tests, updating test commands, or changing continuous integration and delivery workflows.

They keep local tests and automated build checks consistent with the project’s required process.

vios-testing-cicd — Cursor rule for Cursor by NVIDIA-AI-Blueprints

About the project

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.

NVIDIA-AI-Blueprints/video-search-and-summarization · 1,953 stars · on GitHub · build.nvidia.com

Install

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.

Clone the repo

git clone --depth 1 https://github.com/NVIDIA-AI-Blueprints/video-search-and-summarization

Made for: Cursor.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/rules/nvidia-ai-blueprints/video-search-and-summarization/vios-testing-cicd/github.svg)](https://agentmods.dev/rules/nvidia-ai-blueprints/video-search-and-summarization/vios-testing-cicd)

Your own site

<a href="https://agentmods.dev/rules/nvidia-ai-blueprints/video-search-and-summarization/vios-testing-cicd"><img src="https://agentmods.dev/badge/rules/nvidia-ai-blueprints/video-search-and-summarization/vios-testing-cicd/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.

Your own site · 80×15

<a href="https://agentmods.dev/rules/nvidia-ai-blueprints/video-search-and-summarization/vios-testing-cicd"><img src="https://agentmods.dev/badge/rules/nvidia-ai-blueprints/video-search-and-summarization/vios-testing-cicd.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Nothing until a file matches its globs; then the whole rule loads.

When invoked 623 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00000	$0.00623
Opus 5.5	$0.00000	$0.00249
Sonnet 5.5	$0.00000	$0.00125
Haiku 4.5	$0.00000	$0.00062

Measured 1mo ago against content hash 7a5c30a3dcc2, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

vios-testing-cicd 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.

services/vios/.cursor/rules/vios-testing-cicd.mdc · 66 lines

How it starts

The opening of the file, as written. The whole thing — 66 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.

Testing

Unit tests: test/gtests/ -- binary is vst_test, built with -D UNIT_TEST
BDD tests: test/bdd_tests/ -- pytest-bdd, requires a running VIOS service; run via cd test/bdd_tests && poetry run pytest tests/
Use /bdd-test skill to write tests for new features

CI/CD

Pipeline: .gitlab-ci.yml -- stages: coverity -> deploy -> push_helm_chart
/test folder excluded from nspect scans (.nspect-allowlist.toml)
Code review automation: .coderabbit.yaml

Branch Naming Convention

Pattern: <type>/<username>/<ticket-id>-<short-description>

Username and ticket ID are optional. Minimal form: <type>/<short-description>

Rules

Lowercase for type prefix and description (ticket IDs retain their original case)
Use hyphens as word separators (never underscores)
Description: 2-5 words max
Include Jira/GitLab issue ID when one exists
Username segment is optional but recommended for shared repos

Valid type prefixes

Prefix	When to use
`feat/`	New feature or capability
`fix/`	Bug fix
`refactor/`	Code restructuring, no behavior change
`cicd/`	CI/CD, build system, deployment changes
`test/`	Test-only changes
`docs/`	Documentation only
`release/`	Release preparation
`hotfix/`	Urgent production fix

Read the full file on GitHub · 66 lines

Changes

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 · 66 lines · 0 tokens per session scan A 7a5c30a3dcc2

Subscribe to this mod's changes

vios-testing-cicd is a cursor rule published in the GitHub repository NVIDIA-AI-Blueprints/video-search-and-summarization (1,953 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 623 tokens. 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.

CI and CD DevOps and cloud RAG and vectors Testing computer-vision skills video-analytics video-search vlm

vios-testing-cicd