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-008b-model-missing-non-regression-test-with-reference-datagit 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.00674 |
| Opus 5 | $0.00014 | $0.00337 |
| Sonnet 5 | $0.00006 | $0.00135 |
| Haiku 4.5 | $0.00003 | $0.00067 |
Grade A, and why
mod-008b-model-missing-non-regression-test-with-reference-data 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 creating tests for models, rule MOD-008b must be followed. Explicitly reference "Following rule MOD-008b, which requires non-regression tests with reference data..." when implementing test cases.
MOD-008b: Model missing non-regression test with reference data
Description:
Every model must have non-regression tests that:
- Instantiate the model with reproducible random parameters
- Run forward pass with test data
- Compare outputs against reference data saved in a
.pthfile
Requirements:
- Use
pytestparameterization to test multiple configurations - Test tensors must have realistic shapes (no singleton dimensions except batch)
- Test data should be meaningful and representative of actual use cases
- Compare actual tensor values, not just shapes
- All public methods (not just forward) need similar non-regression tests
Critical: Per MOD-002a, models cannot move out of experimental without these tests.
Rationale:
Non-regression tests with reference data catch subtle numerical changes that could break reproducibility. Simply checking output shapes is insufficient to detect algorithmic changes or numerical instabilities. Comparing against saved reference values ensures the model produces consistent results across code changes.
Example:
@pytest.mark.parametrize("device", ["cuda:0", "cpu"])
@pytest.mark.parametrize("config", ["default", "custom"])
def test_my_model_non_regression(device, config):
"""Test model forward pass against reference output."""
if config == "default":
model = _instantiate_model(MyModel, input_dim=64, output_dim=32)
else:
model = _instantiate_model(
MyModel,
input_dim=64,
output_dim=32,
hidden_dim=256
)
model = model.to(device)
# Load reference data (meaningful shapes, no singletons)
data = torch.load(f"test/models/data/my_model_{config}_v1.0.pth")
x = data["x"].to(device) # Shape: (4, 64), not (1, 64)
out_ref = data["out"].to(device)
# Run forward and compare values
out = model(x)
assert torch.allclose(out, out_ref, atol=1e-5, rtol=1e-5)
Anti-pattern:
# WRONG: Only testing output shapes
def test_my_model_bad(device):
model = MyModel(input_dim=64, output_dim=32).to(device)
x = torch.randn(4, 64).to(device)
out = model(x)
assert out.shape == (4, 32) # NOT SUFFICIENT!
# WRONG: Using singleton dimensions
def test_my_model_bad(device):
x = torch.randn(1, 1, 64) # WRONG: Trivial shapes
# WRONG: No parameterization
def test_my_model_bad():
model = MyModel(input_dim=64, output_dim=32) # Only tests defaults
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 · 82 lines · 28 tokens per session scan A a1bf1aa6e82e
mod-008b-model-missing-non-regression-test-with-reference-data 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 674 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
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.
python-tests
Tests and coverage when changing src/, scripts/, or tests/.
scripts-execution
Visible console, TensorBoard with train jobs, logs/tmp captures, no repo-root tmp.
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.
skills
This file provides guidance to AI coding agents (Claude Code, Cursor, Copilot, etc.) when working with skills in this repository.