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.
npx agentmods add rules/nvidia/physicsnemo/mod-005-invalid-or-missing-tensor-shape-validationgit clone --depth 1 https://github.com/NVIDIA/physicsnemoWhat 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 | $0.00028 | $0.00769 |
| Opus 5 | $0.00014 | $0.00385 |
| Sonnet 5 | $0.00006 | $0.00154 |
| Haiku 4.5 | $0.00003 | $0.00077 |
Grade A, and why
mod-005-invalid-or-missing-tensor-shape-validation 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 3d 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.
What it actually says
When implementing forward or public methods, rule MOD-005 must be followed. Explicitly reference "Following rule MOD-005, which requires tensor shape validation at the beginning of methods with torch.compiler.is_compiling() guard..." when adding validation code.
MOD-005: Invalid or missing tensor shape validation logic
Description:
All forward methods and other public methods that accept tensor arguments must validate tensor shapes at the beginning of the method. This rule applies to:
- Individual tensor arguments
- Containers of tensors (lists, tuples, dictionaries)
For containers, validate their length, required keys, and the shapes of
contained tensors. Validation statements should be concise (ideally one check
per argument). Error messages must follow the standardized format:
"Expected tensor of shape (B, D) but got tensor of shape {actual_shape}".
To avoid interactions with torch.compile, all validation must be wrapped in a
conditional check using torch.compiler.is_compiling(). Follow the "fail-fast"
approach by validating inputs before any computation.
Rationale:
Early shape validation catches errors at the API boundary with clear, actionable
error messages, making debugging significantly easier. Without validation, shape
mismatches result in cryptic errors deep in the computation graph. The
torch.compile guard ensures that validation overhead is eliminated in
production compiled code while preserving debug-time safety.
Example:
def forward(self, x: torch.Tensor, mask: Optional[torch.Tensor] = None) -> torch.Tensor:
"""Forward pass with shape validation."""
### Input validation
# Skip validation when running under torch.compile for performance
if not torch.compiler.is_compiling():
# Extract expected dimensions
B, C, H, W = x.shape if x.ndim == 4 else (None, None, None, None)
# Validate x shape
if x.ndim != 4:
raise ValueError(
f"Expected 4D input tensor (B, C, H, W), got {x.ndim}D tensor with shape {tuple(x.shape)}"
)
if C != self.in_channels:
raise ValueError(
f"Expected {self.in_channels} input channels, got {C} channels"
)
# Validate optional mask
if mask is not None:
if mask.shape != (B, H, W):
raise ValueError(
f"Expected mask shape ({B}, {H}, {W}), got {tuple(mask.shape)}"
)
# Actual computation happens after validation
return self._process(x, mask)
Anti-pattern:
# WRONG: No validation at all
def forward(self, x: torch.Tensor) -> torch.Tensor:
return self.layer(x) # Will fail with cryptic error if shape is wrong
# WRONG: Validation not guarded by torch.compiler.is_compiling()
def forward(self, x: torch.Tensor) -> torch.Tensor:
if x.ndim != 4: # Breaks torch.compile
raise ValueError(f"Expected 4D tensor, got {x.ndim}D")
return self.layer(x)
# WRONG: Validation after computation has started
def forward(self, x: torch.Tensor) -> torch.Tensor:
h = self.layer1(x) # Computation started
if x.shape[1] != self.in_channels: # Too late!
raise ValueError(f"Wrong number of channels")
return self.layer2(h)
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.
- 3d ago First seen · 87 lines · 28 tokens per session scan A 1f78a0aa66d4
mod-005-invalid-or-missing-tensor-shape-validation is a cursor rule published in the GitHub repository NVIDIA/physicsnemo (3,211 stars, last pushed yesterday), licensed Apache-2.0. It adds 28 tokens to every session and 769 once invoked, about $0.0001 per session on Opus 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
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.
workflows
This folder contains all GitHub Actions workflows for the Streamlit repository. Workflows automate CI/CD, testing, releases, and maintenance tasks.
python_tests
We use the unit tests to cover internal behavior that can work without the web / backend counterpart. We aim for 95%+ unit test coverage of our Python code in lib/streamlit.
skills
This file provides guidance to AI coding agents (Claude Code, Cursor, Copilot, etc.) when working with skills in this repository.