A command that writes BDD tests for a new VIOS feature. BDD, or behavior-driven development, describes expected behavior in a readable feature file and connects it to pytest-bdd test code.

Use it when adding a VIOS feature and you need a feature file plus pytest-bdd step implementations.

It removes the need to create the behavior description and its Python test steps separately.

bdd-test — Command for Claude Code 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,947 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: Claude Code.

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/commands/nvidia-ai-blueprints/video-search-and-summarization/bdd-test/github.svg)](https://agentmods.dev/commands/nvidia-ai-blueprints/video-search-and-summarization/bdd-test)

Your own site

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

Your own site · 80×15

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

Per session 23 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,012 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.00023	$0.01012
Opus 5.5	$0.00009	$0.00405
Sonnet 5.5	$0.00005	$0.00202
Haiku 4.5	$0.00002	$0.00101

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

Security

Grade A, and why

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

services/vios/.claude/commands/bdd-test.md · 79 lines

How it starts

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

Write BDD tests for the new VIOS feature described by the user.

Project test structure:

Feature files (Gherkin): test/bdd_tests/features/<category>/<name>.feature
Step implementations: test/bdd_tests/tests/<category>/test_<name>.py
Shared fixtures: test/bdd_tests/tests/unit_tests/conftest.py (for unit tests) or test/bdd_tests/tests/<category>/conftest.py
Shared utils: test/bdd_tests/tests/unit_tests/unit_test_utils.py, test/bdd_tests/tests/test_utils.py
Config loaded from test/bdd_tests/config.json via api_config and unit_test_params fixtures

Framework: pytest-bdd with scenarios() binding. Each test file imports the feature file via scenarios("../../../features/...").

Steps before writing:

Check for duplicates first. Before adding any scenario, search the existing suite for an equivalent test so you don't reintroduce one that already passes or is owned by another branch:
- Grep feature files for the API path, the error code, or the behavior phrase (e.g., grep -rn "fullLength" test/bdd_tests/features/).
- Grep step impls for the same (grep -rn "fullLength" test/bdd_tests/tests/).
- Check other branches if the user mentions one (git branch -a | grep <topic> then git show <branch>:<path>). The bug-fix branches under fix/prakhar/... and fix/<user>/... often carry regression tests that are not yet on v2.1.
- If a similar test exists, extend it with a new Scenario or Scenario Outline row instead of creating a parallel test file. Two files binding to the same .feature will collect duplicate tests and at least one will fail at runtime because step impls are split across modules.
- If the requested scenario is already covered, tell the user where and stop — do not duplicate.
Read the feature file for the closest existing module (e.g., sensor_management_api.feature) to match Gherkin style.
Read the corresponding test file (e.g., test_sensor_management_api.py) to match step implementation patterns.
Read unit_test_utils.py to understand available helpers (api_get, UnitTestContext, validators).
Understand the new feature's REST API endpoints (ask the user or read the relevant source under src/framework/apis/ or src/modules/).

Read the full file on GitHub · 79 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 · 79 lines · 23 tokens per session scan A 2c533686be33

Subscribe to this mod's changes

bdd-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 23 tokens to every session and 1,012 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.

RAG and vectors Testing computer-vision skills video-analytics video-search vlm

bdd-test