mod-005-invalid-or-missing-tensor-shape-validation

mod-005-invalid-or-missing-tensor-shape-validation is a cursor rule for Cursor from NVIDIA/physicsnemo. It costs 28 tokens per session (769 once invoked), scanned A, original, Apache-2.0.

A coding rule requiring public methods and model forward methods to check incoming tensor shapes before doing any computation. A tensor is a multi-dimensional block of numerical data.

In plain words
What is it for?
Use it when implementing methods that accept tensors or containers of tensors, including checks for lengths, keys, and contained shapes.
Why use it?
Early checks turn confusing downstream errors into clear messages about the expected and received shapes, while accounting for compiled code.

Cursor rule for Cursor ✓ vendor

Written for Cursor: installed under .cursor/.

Good fit Use it when implementing methods that accept tensors or containers of tensors, including checks for lengths, keys, and contained shapes.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/nvidia/physicsnemo/mod-005-invalid-or-missing-tensor-shape-validation
About the project

PhysicsNeMo is an open-source PyTorch framework for creating, training, and fine-tuning machine-learning models for physics, scientific computing, and engineering. Researchers and engineers use its reusable components and training recipes for applications such as aerodynamics, weather forecasting, structural mechanics, geophysics, and thermal design. The catalogue entries provide rules and skills for working with PhysicsNeMo projects.

NVIDIA/physicsnemo · 3,418 stars · on GitHub · developer.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/physicsnemo

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.

agentmods badge for mod-005-invalid-or-missing-tensor-shape-validation

README.md
[![agentmods](https://agentmods.dev/badge/rules/nvidia/physicsnemo/mod-005-invalid-or-missing-tensor-shape-validation/github.svg)](https://agentmods.dev/rules/nvidia/physicsnemo/mod-005-invalid-or-missing-tensor-shape-validation)
Your own site
<a href="https://agentmods.dev/rules/nvidia/physicsnemo/mod-005-invalid-or-missing-tensor-shape-validation"><img src="https://agentmods.dev/badge/rules/nvidia/physicsnemo/mod-005-invalid-or-missing-tensor-shape-validation/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.

agentmods 80×15 button for mod-005-invalid-or-missing-tensor-shape-validation

Your own site · 80×15
<a href="https://agentmods.dev/rules/nvidia/physicsnemo/mod-005-invalid-or-missing-tensor-shape-validation"><img src="https://agentmods.dev/badge/rules/nvidia/physicsnemo/mod-005-invalid-or-missing-tensor-shape-validation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 28 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 769 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00028 $0.00769
Opus 5.5 $0.00011 $0.00308
Sonnet 5.5 $0.00006 $0.00154
Haiku 4.5 $0.00003 $0.00077

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

Security

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 2mo 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.

.cursor/rules/mod-005-invalid-or-missing-tensor-shape-validation.mdc · 87 lines

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

  1. 2mo ago First seen · 87 lines · 28 tokens per session scan A 1f78a0aa66d4

Subscribe to this mod's changes

mod-005-invalid-or-missing-tensor-shape-validation is a cursor rule published in the GitHub repository NVIDIA/physicsnemo (3,418 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.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.

Related

mod-005-invalid-or-missing-tensor-shape-validation compared with cursor rules from other repositories

mod-005-invalid-or-missing-tensor-shape-validation next to 6 cursor rules from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
mod-005-invalid-or-missing-tensor-shape-validationNVIDIA/physicsnemoCursor rule3.4kyesterdayApache-2.0A28Cursor
python_libstreamlit/streamlitCursor rule46kyesterdayApache-2.0A0Cursor
typescriptstreamlit/streamlitCursor rule46kyesterdayApache-2.0A5,351Cursor
specsstreamlit/streamlitCursor rule46kyesterdayApache-2.0A0Cursor
workflowsstreamlit/streamlitCursor rule46kyesterdayApache-2.0A0Cursor
skillsstreamlit/streamlitCursor rule46kyesterdayApache-2.0A0Cursor
python_testsstreamlit/streamlitCursor rule46kyesterdayApache-2.0A0Cursor